Re:Confirmed: Windows Azure downtime caused by leap-day bug
by lysium on Thursday March 01, 2012 @02:30PM
(#3653615)
I mean there are two t (0th March and Feb 29th) that print as Feb 29 (so any user seeing the value of those t may rightly assume they are the same), but for one t one month earlier is Jan 31, while for the other t one month earlier is Jan 29.
Of course, internally, all is correct, but for the user, things may behave strangely.
The second time you have, is 0th February. So that underflows back to the previous day, Jan 31st -- the day before February 1st.