[26511] in North American Network Operators' Group
Re: Netscape JavaScript getYear() problem? CONFIRMED
daemon@ATHENA.MIT.EDU (Lloyd Taylor)
Sun Jan 2 00:39:45 2000
Date: Sat, 1 Jan 2000 21:38:23 -0800 (PST)
From: Lloyd Taylor <ltaylor@keynote.com>
To: Will Pierce <willp@nbinteractive.com>
Cc: nanog@merit.edu
In-Reply-To: <025d01bf54db$03917aa0$fdd6f4d1@willp>
Message-ID: <Pine.GSO.4.05.10001012136150.21452-100000@mailnew>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
We've found the same thing, and have coded around it for our
software. I'll post details as soon as I get them from our
Engineering department.
--Lloyd Taylor
VP Operations
Keynote Systems
On Sat, 1 Jan 2000, Will Pierce wrote:
> Date: Sat, 1 Jan 2000 23:37:01 -0500
> From: Will Pierce <willp@nbinteractive.com>
> To: nanog@merit.edu
> Subject: Netscape JavaScript getYear() problem? Also bad JavaScript on CNN.
>
>
> It appears that the javascript function "getYear" in the Date class
> is inconsistent between Java implementations. This happens when
> getYear() is called with no arguments, in other words, when getYear()
> is queried for the current year.
