On 11 mai, 22:26, Andy Champ <no....@[EMAIL PROTECTED]
> wrote:
> James Kanze wrote:
> >> I always feel there's a case for doing all my releases after
> >> the 12th of the month...
> > And of course, you make very sure you test the 29th Feb. in a
> > leap year before releasing as well. Just as when time is
> > involved, you make sure you test 2:30 AM the day you go on, and
> > the day you go off summer time. And on a 32 bit machine, you'll
> > definitely test some dates after 2038.
> Sure. But you miss my point.
Not really.
> A release date of 1/12/08 could be in the future or the past;
> a release data of 1/13/08 (or 13/1/08) is definitely in the
> past!
> I was writing code long before the Millennium Bug went pop
> very quietly...
So was I.
All I can say is that you made a valid point: that one has to
test all of the special cases. And all I wanted to add is that
that there are a lot of special cases, when it comes to dates
(and time).
I added it because I suspect that a lot of programmers forget to
test them. Just as they don't take into account that in most of
the world, the standard format for entering dates is dd/mm/YYYY.
(Or dd-mm-YYYY. Or, if you take into account ISO: YYYYmmdd.)
--
James Kanze (GABI Software) email:james.kanze@[EMAIL PROTECTED]
en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34
|
