New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug with Time::Local #2094
Comments
From jasonn@noble.vservers.comHello. i'm not sure if this is the correct place to report this, if it I have discovered a possible bug with the Time::Local::timelocal The problem seems to only occur using the date 4/2/2000 at 1:00am and I've tried narrowing it down to see what the problem could be, and it Thanks for any light you can shed on the subject. Jason -- Reproduction: use Time::Local; $curr_month = 0; # Don't forget it's 0-11, so 3 is April $end_time = timelocal(59,59,1,$curr_day,$curr_month,$curr_year); @tmp = localtime($begin_time); $end_time = timelocal(59,59,2,$curr_day,$curr_month,$curr_year); @tmp = localtime($begin_time); Output: |
From @tamiasOn Thu, Jun 15, 2000 at 12:31:25PM -0700, Jason Noble wrote:
Daylight Savings Time began at 2am on April 2nd this year. Ronald |
From [Unknown Contact. See original ticket]I'd suspect it has something to do with DST, and the fact that there IS no #!/usr/local/bin/perl $ perl testdst.pl At 12:31 PM 6/15/00 -0700, Jason Noble wrote:
|
From [Unknown Contact. See original ticket]This brings up something else though... the statement from the documentation: "These routines are quite efficient and yet are always Is not entirely accurate, because: @foo = (0,0,2,2,3,100); Perhaps instead of "fudging" there, it should determine if it's in the D |
From [Unknown Contact. See original ticket]On Thu, 15 Jun 2000, Derek J. Balling wrote:
Hey, I thought we were DONE with the string decrement thread. :-) John. |
From [Unknown Contact. See original ticket]That makes total sense now. Sorry I didn't come up with that on my own. Jason -- "Derek J. Balling" wrote:
|
Migrated from rt.perl.org#3384 (status was 'resolved')
Searchable as RT3384$
The text was updated successfully, but these errors were encountered: