8 our @ISA = qw( Exporter );
9 our @EXPORT = qw( timegm timelocal );
10 our @EXPORT_OK = qw( timegm_nocheck timelocal_nocheck );
17 # Determine breakpoint for rolling century
18 my $ThisYear = (localtime())[5];
19 my $NextCentury = int($ThisYear / 100) * 100;
20 my $Breakpoint = ($ThisYear + 50) % 100;
21 $NextCentury += 100 if $Breakpoint < 50;
23 our(%Options, %Cheat);
30 elsif ($date[5] >= 0 && $date[5] < 100) {
31 $date[5] -= 100 if $date[5] > $Breakpoint;
32 $date[5] += $NextCentury;
34 my $ym = pack('C2', @date[5,4]);
35 my $cheat = $Cheat{$ym} || &cheat($ym, @date);
40 + ($date[3]-1) * $DAY;
44 local $Options{no_range_check} = 1;
52 my (@lt) = localtime($t);
53 my (@gt) = gmtime($t);
54 if ($t < $DAY and ($lt[5] >= 70 or $gt[5] >= 70 )) {
55 # Wrap error, too early a date
62 my $tzsec = ($gt[1] - $lt[1]) * $MIN + ($gt[2] - $lt[2]) * $HR;
67 elsif($gt[5] > $lt[5]) {
71 $tzsec += ($gt[7] - $lt[7]) * $DAY;
74 $tzsec += $HR if($lt[8]);
76 my $time = $t + $tzsec;
77 my @test = localtime($time + ($tt - $t));
78 $time -= $HR if $test[2] != $_[2];
82 sub timelocal_nocheck {
83 local $Options{no_range_check} = 1;
89 my($sec, $min, $hour, $day, $month, $year) = @date;
90 unless ($Options{no_range_check}) {
91 croak "Month '$month' out of range 0..11" if $month > 11 || $month < 0;
92 my $md = (31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31)[$month];
93 $md++ if $month == 1 &&
94 $year % 4 == 0 && ($year % 100 > 0 || $year % 400 == 100); # leap
95 croak "Day '$day' out of range 1..$md" if $day > $md || $day < 1;
96 croak "Hour '$hour' out of range 0..23" if $hour > 23 || $hour < 0;
97 croak "Minute '$min' out of range 0..59" if $min > 59 || $min < 0;
98 croak "Second '$sec' out of range 0..59" if $sec > 59 || $sec < 0;
101 my @g = gmtime($guess);
104 while (my $diff = $year - $g[5]) {
106 croak "Can't handle date (".join(", ",@date).")" if ++$counter > 255;
107 $guess += $diff * (363 * $DAY);
109 if (($thisguess = "@g") eq $lastguess){
110 croak "Can't handle date (".join(", ",@date).")";
111 #date beyond this machine's integer limit
113 $lastguess = $thisguess;
115 while (my $diff = $month - $g[4]) {
117 croak "Can't handle date (".join(", ",@date).")" if ++$counter > 255;
118 $guess += $diff * (27 * $DAY);
120 if (($thisguess = "@g") eq $lastguess){
121 croak "Can't handle date (".join(", ",@date).")";
122 #date beyond this machine's integer limit
124 $lastguess = $thisguess;
126 my @gfake = gmtime($guess-1); #still being sceptic
127 if ("@gfake" eq $lastguess){
128 croak "Can't handle date (".join(", ",@date).")";
129 #date beyond this machine's integer limit
132 $guess -= $g[0] * $SEC + $g[1] * $MIN + $g[2] * $HR + $g[3] * $DAY;
133 $Cheat{$ym} = $guess;
142 Time::Local - efficiently compute time from local and GMT time
146 $time = timelocal($sec,$min,$hour,$mday,$mon,$year);
147 $time = timegm($sec,$min,$hour,$mday,$mon,$year);
151 These routines are the inverse of built-in perl functions localtime()
152 and gmtime(). They accept a date as a six-element array, and return
153 the corresponding time(2) value in seconds since the Epoch (Midnight,
154 January 1, 1970). This value can be positive or negative.
156 It is worth drawing particular attention to the expected ranges for
157 the values provided. The value for the day of the month is the actual day
158 (ie 1..31), while the month is the number of months since January (0..11).
159 This is consistent with the values returned from localtime() and gmtime().
161 The timelocal() and timegm() functions perform range checking on the
162 input $sec, $min, $hour, $mday, and $mon values by default. If you'd
163 rather they didn't, you can explicitly import the timelocal_nocheck()
164 and timegm_nocheck() functions.
166 use Time::Local 'timelocal_nocheck';
169 # The 365th day of 1999
170 print scalar localtime timelocal_nocheck 0,0,0,365,0,99;
172 # The twenty thousandth day since 1970
173 print scalar localtime timelocal_nocheck 0,0,0,20000,0,70;
175 # And even the 10,000,000th second since 1999!
176 print scalar localtime timelocal_nocheck 10000000,0,0,1,0,99;
179 Your mileage may vary when trying these with minutes and hours,
180 and it doesn't work at all for months.
182 Strictly speaking, the year should also be specified in a form consistent
183 with localtime(), i.e. the offset from 1900.
184 In order to make the interpretation of the year easier for humans,
185 however, who are more accustomed to seeing years as two-digit or four-digit
186 values, the following conventions are followed:
192 Years greater than 999 are interpreted as being the actual year,
193 rather than the offset from 1900. Thus, 1963 would indicate the year
194 Martin Luther King won the Nobel prize, not the year 2863.
198 Years in the range 100..999 are interpreted as offset from 1900,
199 so that 112 indicates 2012. This rule also applies to years less than zero
200 (but see note below regarding date range).
204 Years in the range 0..99 are interpreted as shorthand for years in the
205 rolling "current century," defined as 50 years on either side of the current
206 year. Thus, today, in 1999, 0 would refer to 2000, and 45 to 2045,
207 but 55 would refer to 1955. Twenty years from now, 55 would instead refer
208 to 2055. This is messy, but matches the way people currently think about
209 two digit dates. Whenever possible, use an absolute four digit year instead.
213 The scheme above allows interpretation of a wide range of dates, particularly
214 if 4-digit years are used.
216 Please note, however, that the range of dates that can be actually be handled
217 depends on the size of an integer (time_t) on a given platform.
218 Currently, this is 32 bits for most systems, yielding an approximate range
219 from Dec 1901 to Jan 2038.
221 Both timelocal() and timegm() croak if given dates outside the supported
224 =head1 IMPLEMENTATION
226 These routines are quite efficient and yet are always guaranteed to agree
227 with localtime() and gmtime(). We manage this by caching the start times
228 of any months we've seen before. If we know the start time of the month,
229 we can always calculate any time within the month. The start times
230 themselves are guessed by successive approximation starting at the
231 current time, since most dates seen in practice are close to the
232 current date. Unlike algorithms that do a binary search (calling gmtime
233 once for each bit of the time value, resulting in 32 calls), this algorithm
234 calls it at most 6 times, and usually only once or twice. If you hit
235 the month cache, of course, it doesn't call it at all.
237 timelocal() is implemented using the same cache. We just assume that we're
238 translating a GMT time, and then fudge it when we're done for the timezone
239 and daylight savings arguments. Note that the timezone is evaluated for
240 each date because countries occasionally change their official timezones.
241 Assuming that localtime() corrects for these changes, this routine will
242 also be correct. The daylight savings offset is currently assumed
247 The whole scheme for interpreting two-digit years can be considered a bug.
249 Note that the cache currently handles only years from 1900 through 2155.
251 The proclivity to croak() is probably a bug.