Cross Reference: /libcore/luni/src/main/java/libcore/util/ZoneInfo.java

Lines Matching defs:it
45  * and storing it a representation to support the {@link TimeZone} and {@link GregorianCalendar}
51  * <p>This class does not use all the information from the {@code tzfile}; it uses:
53  * (described by {@code struct ttinfo}) it uses {@code tt_gmtoff} and {@code tt_isdst}. Note, that
55  * the same meaning as Java. The prose following the definition makes it clear that the {@code long}
59  * 69 years either side of the epoch (1st Jan 1970 00:00:00) that means that it cannot handle any
91      * using it for the lifetime of the instance does not match the contract of the
92      * {@link TimeZone#useDaylightTime()} method but it appears to be what the RI does and that
93      * method is not particularly useful when it comes to historical or future times as it does not
105      * <p>This should be final but is not because it may need to be fixed up by
181     public static ZoneInfo readTimeZone(String id, BufferIterator it, long currentTimeMillis)
186         int tzh_magic = it.readInt();
192         it.skip(28);
195         int tzh_timecnt = it.readInt();
204         int tzh_typecnt = it.readInt();
214         it.skip(4); // Skip tzh_charcnt.
217         // integers since it's easier to compare them against 64 bit inputs (see getOffset
223         it.readIntArray(transitions32, 0, transitions32.length);
236         it.readByteArray(type, 0, type.length);
248             gmtOffsets[i] = it.readInt();
249             byte isDst = it.readByte();
261             it.skip(1);
305             // Check to see if the last DST transition is in the future or the past. If it is in
306             // the past then we treat it as if it doesn't exist, at least for the purposes of
317             // We don't care if they've historically used it: most places have at least once.
323                 // The last DST transition is before now so treat it as if it doesn't exist.
335             // This isn't generally useful, but it's exposed by TimeZone.getDSTSavings.
468      * for positive numbers it produces a time in seconds that precedes the time in milliseconds
469      * for negative numbers it can produce a time in seconds that follows the time in milliseconds.
495      * for negative numbers it produces a time in seconds that follows the time in milliseconds
496      * for positive numbers it can produce a time in seconds that precedes the time in milliseconds.
704         // Unfortunately, it cannot represent an initial state with a zero day and would
705         // automatically normalize it, so we must copy values into and out of it as needed.
728          * <p>When going from an instant to a wall time it is always unambiguous because there
831                     // This is treated as a special case to get it out of the way:
832                     // When a caller has set isDst == -1 it means we can return the first match for
843                 // 2) If it fails, isDst is assumed to be incorrect and adjustments are made to see
878          * {@code targetInterval}, apply it, and see if we are still in {@code targetInterval}. If
967          * If {@code this.isDst == -1} it means that any offset can be used.
971          * transition can be used, if it is 0 or 1 the offset used must match {@code this.isDst}.
974          * in seconds if a match has been found and modifies fields, or it returns {@code null} and
1023                             // This always returns the first OffsetInterval it finds that matches
1188      * <p>Wall-time means "as it would appear locally in the timezone in which it applies".
1198      * in the offset it is necessary to <em>subtract</em> the {@code totalOffsetSeconds}.