From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,92471489ebbc99c6 X-Google-Attributes: gid103376,public From: Dave Wood Subject: Re: Y2K Issues (well, not really...) Date: 1998/10/27 Message-ID: <36369015.BCA1B1C9@cts.com>#1/1 X-Deja-AN: 405794128 Cache-Post-Path: wagasa.cts.com!unknown@arniek.cts.com Content-Transfer-Encoding: 7bit References: <713oes$dbn$1@nnrp1.dejanews.com> Content-Type: text/plain; charset=us-ascii Organization: Deja Vous Productions Mime-Version: 1.0 Reply-To: dpw@cts.com Newsgroups: comp.lang.ada Date: 1998-10-27T00:00:00+00:00 List-Id: Tucker Taft wrote: > > : In article <7125a8$e7u$1@nnrp1.dejanews.com>, > : dennison@telepath.com wrote: > > : > Don't be quite so hard on uSoft. ObjectAda 7.1.1 had this exact same problem. > > That surprises me, because the package Calendar we have shipped with > our Ada 95 front end since the beginning has the following leap_year > function (original comment included): [snip] > > : > I understand it has been fixed in the current release, though. > > That's good. Maybe there is an interesting story here (or perhaps > this whole thing is apocryphal?). I don't know how good the story is - that's for others to decide! To me, I'm afraid, the story is no more exciting than any other ordinary bug story - no major database corruptions, power outages, downed airlines, or other significant catastophes. We leave those to C code. :) The problem had nothing to do with whether or not the year 2000 is a leap year. As Tucker has said, our runtime understands that this is so. The problem was that our implementation of Ada.Real_Time caused an internal runtime exception when any Ada application was executed on *any* leap year day, 1904, 1996, 2000, 2060, etc. It just happened to be caught during our routine year 2000 testing which includes leap tests. Although the issue was detected just prior to the current 7.1.2 release, we felt no great need to delay that release to include a fix, given that the problem is unlikely to manifest itself for another 1.5 years. The fix is in the upcoming 7.1.3 release. For those who might have an immediate need, a patch is posted on our web site in the support area. -- Dave Wood, Aonix -- Product Manager, ObjectAda for Windows -- http://www.aonix.com