I wonder if there is a technical reason for this. Perhaps it's because months aren't the same size, while days, hours, minutes, and seconds are almost always the same size. Even so, its current behavior still seems strange.. at least it could try to do something reasonable with months > 12 instead of reducing mod 12 as it does now.Your mileage may vary when trying these with minutes and hours, and it doesn't work at all for months.# The 365th day of 1999 print scalar localtime timelocal_nocheck 0,0,0,365,0,99; # The twenty thousandth day since 1970 print scalar localtime timelocal_nocheck 0,0,0,20000,0,70; # And even the 10,000,000th second since 1999! print scalar localtime timelocal_nocheck 10000000,0,0,1,0,99;
blokhead
In reply to Re: timelocal_nocheck: bug or wrongly understood
by blokhead
in thread timelocal_nocheck: bug or wrongly understood
by borisz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |