[ILUG] [OT] Netscrape Javascript not Y2k compatible

[Shane Dempsey]

So Netscape forgot that the millenium would
end aswell.
This kind of error generally occurs when your working with C / C++ strings
and try to be  a bit to clever.
They probably tested for the year < 100 and
then appended the two digits to a "19" string.
With that logic 1910 would also have been possible >:-))

Inteerstingly enough the only y2k bug that this weary mind can think of was
a inability to call any dodgyfone number
in the waterford area last night.
( Well I tried 3 of them ) Did anybody else have the same
trouble with esat ?

Totally OT but the coffee machine stopped working but it was just a fuse.
Happened around midnight though. Now that really was a disaster.

    ...shane

sdempsey at iol.ie sdempsey at emhain.wit.ie
sdempsey at tssg.wit.ie
win v lin is like auto versus stick shift. One is easy but
lacks control , the other gives greater speed but is
hell in traffic - overheard

----- Original Message -----
From: Robert Elliott (Admin) <rde at leviathan.irelands-web.ie>
Cc: Linux Usergroup <ilug at linux.ie>
Sent: Saturday, January 01, 2000 5:44 PM
Subject: Re: [ILUG] [OT] Netscrape Javascript not Y2k compatible


> has it you add 1900. So was the javascript thingy in nescape written in
> perl, I wonder? Anyway, I'd guess that some idiot put in half a check;
> something along the lines of 'if year < 100 year += 1900'.
>
> Not your traditional y2k bug, but more of some dope half-thinking about
> the millennium and implementing what our french cousins would call 'un
> solution demi-arsee'.
> >