4 ms·
If you really want to stress test time handling code, try to get it to accept Feburary 29, 1900 and Feburary 29, 2000. The first doesn't exist but the second do
by tomjen3 14y ago
If you really want to stress test time handling code, try to get it to accept Feburary 29, 1900 and Feburary 29, 2000. The first doesn't exist but the second does.
But really, with regards to time use whatever library came with you programming language.
- grimlck 14y agoThat will stress it a bit, but to really torture it, see if it accepts 2012 June 30 23:59:60
- brazzy 14y agoOr June 1st 1905 00:02:00 in Singapore.
- aurelianito 14y agoI had to google this one. http://www.timeanddate.com/worldclock/clockchange.html?n=236&year=1905 http://www.timeanddate.com/worldclock/clockchange.html?n=236...
- hcarvalhoalves 14y agoNow that's just mean! ;)
- rplnt 14y agoWell, you don't know if 31.12.2015 will have a 23:59:60 or no. These seconds are announced just prior to being added, the system couln't possibly know it.
- dredmorbius 14y agoObviously no. That's after the Mayapocolypse.
- obtu 14y agoJune is already decided. We'll know either way about the December second when the next bulletin C is published, sometime next July: http://hpiers.obspm.fr/iers/bul/bulc/ http://hpiers.obspm.fr/iers/bul/bulc/
- yxhuvud 14y agoOr 30th February 1712.