Keith Winstein said: > Hmm, in practice I think the plan to simply fail with an error is > going to be a non-starter. Plenty of applications need to record dates > more than six months in the future; e.g. in a calendar program, the > user will want to schedule a meeting for August 1, 2012, from 9 a.m. > EDT to 10 a.m. EDT.
Actually, let's suppose it was March, not August. The user probably wants to schedule a meeting for 26th March 2013, 09:00 ET to 10:00 ET. Now the user doesn't care at this point whether ET is EST or EDT. If the changeover date changes between now and then, they want the appointment to remain ET. > The program will want to do all the normal things > -- calculate the duration of the meeting, how far in the future it is > (so it can put it in sorted order along with the other events of that > day), etc. Right. And they want all the ET events sorted by ET, irrespective of whether "daylight saving time" is in effect or not. -- Clive D.W. Feather | If you lie to the compiler, Email: cl...@davros.org | it will get its revenge. Web: http://www.davros.org | - Henry Spencer Mobile: +44 7973 377646 _______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com http://six.pairlist.net/mailman/listinfo/leapsecs
