Lines Matching full:timestamps

150 for all timestamps;
151 otherwise, for timestamps before the first occurrence time,
177 is known to support this feature for timestamps past 2037,
181 and older timestamps need not be handled accurately.
235 timestamps after this expiration are unreliable in that future
237 the added leap seconds will change how post-expiration timestamps are treated.
262 agree with current readers about timestamps within the
272 post-expiration timestamps, or process them as if the expiration
321 made to limit glitches to rarely used timestamps and allow
335 version 2+ data even if the reader's native timestamps have only
339 timestamps after a version 3 or higher file's last transition, because
343 than necessary, so that only far-future timestamps are
369 timestamps from the time type of the last transition.
374 and use its proleptic TZ string to calculate all timestamps.
375 Although this approach often works for current and future timestamps,
376 it obviously has problems with past timestamps,
377 and even for current timestamps it can fail for settings like
382 which should be used only for timestamps after the last
385 Some readers do not use time type 0 for timestamps before
391 Some readers mishandle timestamps before the first
393 Readers that support only 32-bit timestamps are likely to be
402 Timestamps less than \-2**59 are not recommended.
444 Some readers generate ambiguous timestamps for positive leap seconds
460 Some readers do not support negative timestamps.
464 Some readers mishandle timestamps before the first
466 Readers that do not support negative timestamps are likely to