Closed GoogleCodeExporter closed 9 years ago
The bug arose because the original version of the code was for a signed time_t,
for which this issue doesn't arise (2100 is outside the range, and 1900 is just
outside as well). We're using unsigned time_t now, so 2100 does have to be
handled. I've checked in code and tests for this.
Original comment by ersm...@hfx.eastlink.ca
on 13 Mar 2012 at 1:51
Original issue reported on code.google.com by
jsden...@gmail.com
on 5 Mar 2012 at 7:30