1Time::Local(3pm) Perl Programmers Reference Guide Time::Local(3pm)
2
6 Time::Local - efficiently compute time from local and GMT time
7
9 $time = timelocal($sec,$min,$hour,$mday,$mon,$year);
10 $time = timegm($sec,$min,$hour,$mday,$mon,$year);
11
13 This module provides functions that are the inverse of built-in perl
14 functions "localtime()" and "gmtime()". They accept a date as a six-
15 element array, and return the corresponding time(2) value in seconds
16 since the system epoch (Midnight, January 1, 1970 GMT on Unix, for
17 example). This value can be positive or negative, though POSIX only
18 requires support for positive values, so dates before the system's
19 epoch may not work on all operating systems.
20 It is worth drawing particular attention to the expected ranges for the
22 values provided. The value for the day of the month is the actual day
23 (ie 1..31), while the month is the number of months since January
24 (0..11). This is consistent with the values returned from "localtime()"
25 and "gmtime()".
26
28 "timelocal()" and "timegm()"
29 This module exports two functions by default, "timelocal()" and
30 "timegm()".
31 The "timelocal()" and "timegm()" functions perform range checking on
33 the input $sec, $min, $hour, $mday, and $mon values by default.
34 "timelocal_nocheck()" and "timegm_nocheck()"
36 If you are working with data you know to be valid, you can speed your
37 code up by using the "nocheck" variants, "timelocal_nocheck()" and
38 "timegm_nocheck()". These variants must be explicitly imported.
39 use Time::Local 'timelocal_nocheck';
41 # The 365th day of 1999
43 print scalar localtime timelocal_nocheck 0,0,0,365,0,99;
44 If you supply data which is not valid (month 27, second 1,000) the
46 results will be unpredictable (so don't do that).
47 Year Value Interpretation
49 Strictly speaking, the year should be specified in a form consistent
50 with "localtime()", i.e. the offset from 1900. In order to make the
51 interpretation of the year easier for humans, however, who are more
52 accustomed to seeing years as two-digit or four-digit values, the
53 following conventions are followed:
54 · Years greater than 999 are interpreted as being the actual year,
56 rather than the offset from 1900. Thus, 1964 would indicate the
57 year Martin Luther King won the Nobel prize, not the year 3864.
58 · Years in the range 100..999 are interpreted as offset from 1900, so
60 that 112 indicates 2012. This rule also applies to years less than
61 zero (but see note below regarding date range).
62 · Years in the range 0..99 are interpreted as shorthand for years in
64 the rolling "current century," defined as 50 years on either side
65 of the current year. Thus, today, in 1999, 0 would refer to 2000,
66 and 45 to 2045, but 55 would refer to 1955. Twenty years from now,
67 55 would instead refer to 2055. This is messy, but matches the way
68 people currently think about two digit dates. Whenever possible,
69 use an absolute four digit year instead.
70 The scheme above allows interpretation of a wide range of dates,
72 particularly if 4-digit years are used.
73 Ambiguous Local Times (DST)
75 Because of DST changes, there are many time zones where the same local
76 time occurs for two different GMT times on the same day. For example,
77 in the "Europe/Paris" time zone, the local time of 2001-10-28 02:30:00
78 can represent either 2001-10-28 00:30:00 GMT, or 2001-10-28 01:30:00
79 GMT.
80 When given an ambiguous local time, the timelocal() function should
82 always return the epoch for the earlier of the two possible GMT times.
83 Non-Existent Local Times (DST)
85 When a DST change causes a locale clock to skip one hour forward, there
86 will be an hour's worth of local times that don't exist. Again, for the
87 "Europe/Paris" time zone, the local clock jumped from 2001-03-25
88 01:59:59 to 2001-03-25 03:00:00.
89 If the "timelocal()" function is given a non-existent local time, it
91 will simply return an epoch value for the time one hour later.
92
94 These routines are quite efficient and yet are always guaranteed to
95 agree with "localtime()" and "gmtime()". We manage this by caching the
96 start times of any months we've seen before. If we know the start time
97 of the month, we can always calculate any time within the month. The
98 start times are calculated using a mathematical formula. Unlike other
99 algorithms that do multiple calls to "gmtime()".
100 The "timelocal()" function is implemented using the same cache. We just
102 assume that we're translating a GMT time, and then fudge it when we're
103 done for the timezone and daylight savings arguments. Note that the
104 timezone is evaluated for each date because countries occasionally
105 change their official timezones. Assuming that "localtime()" corrects
106 for these changes, this routine will also be correct.
107
109 The whole scheme for interpreting two-digit years can be considered a
110 bug.
111
113 Support for this module is provided via the datetime@perl.org email
114 list. See http://lists.perl.org/ for more details.
115 Please submit bugs to the CPAN RT system at
117 http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Time-Local or via email
118 at bug-time-local@rt.cpan.org.
119
121 Copyright (c) 1997-2003 Graham Barr, 2003-2007 David Rolsky. All
122 rights reserved. This program is free software; you can redistribute
123 it and/or modify it under the same terms as Perl itself.
124 The full text of the license can be found in the LICENSE file included
126 with this module.
127
129 This module is based on a Perl 4 library, timelocal.pl, that was
130 included with Perl 4.036, and was most likely written by Tom
131 Christiansen.
132 The current version was written by Graham Barr.
134 It is now being maintained separately from the Perl core by Dave
136 Rolsky, <autarch@urth.org>.
137perl v5.12.4 2011-06-20 Time::Local(3pm)