Lines Matching full:timestamps
40 whose clocks all agree about timestamps that occur after the <a
59 with current and future timestamps in the traditional North
64 Applications that also deal with past timestamps in the mountain time
68 time but differs from other timezones for some timestamps after 1970.
73 because most systems support timestamps before 1970 and could
348 timestamps correctly and it increased maintenance burden.
367 Applications that process only timestamps from now on can instead use the file
495 The others are for timestamps before 1960,
559 Use current abbreviations for older timestamps to avoid confusion.
565 timestamps as this is less confusing for modern users and avoids
619 timestamps, and current predictions
799 standardized for older timestamps.
806 timestamps, <abbr>UTC</abbr> was not defined until 1960, so
808 timestamps that might predate 1960.
811 interpretation of older timestamps can be problematic when
854 database's pre-1970 and future timestamps are either wrong or
917 timestamps, particularly for timezones
1011 mishandles some timestamps before 2008.
1173 not suffice to handle many real-world timestamps.
1205 <code>mktime</code> to disambiguate timestamps near
1326 offsets or abbreviations for timestamps, as data entries are often
1352 needed to resolve timestamps from 1972 through 2035,
1391 To convert an application's <code>time_t</code> timestamps to or from
1392 POSIX <code>time_t</code> timestamps (for use when, say,
1393 embedding or interpreting timestamps in portable