|
PureBytes Links
Trading Reference Links
|
>It is not a bug.
The hell it isn't a bug! All software which is not Y2K compliant will flat out
cease to work at midnight on Dec 31, 1999 and the developers knew it when they
wrote the software. This applies to all software which uses dates, not just
Omega's. Of course, there were undoubtedly a large number of software developers
who figured the Y2K limitation would simply give them a chance to sell an
upgrade to fix the problem.
>It is simply the way all software reads dates.
This is not the way all software reads dates. Four digit years have been around
for just under a thousand years. Only software which has been designed to save
space in files or on screen by use of 2 digit years suffers from this problem. I
personally designed/wrote a lot of 2 digit year systems back in the 60's because
our mainframes were 16k bytes and big disks were under 20 meg bytes. By the time
the PC revolution was well underway in the early 80's, we were using 4 digit
years in our files and just displaying the last two to conserve screen space. By
the late 80's, virtually all of the major mainframe and PC database packages
(Total, DB2, Oracle, etc.) automatically stored all dates internally in 4 digit
format. By the time the 90's hit, all software developers knew the Y2K problem
was less than a decade away. There is no excuse for software written since 1990
which can not accommodate 4 digit years in the database (no exceptions) and
either accommodate 4 digit years in the display or intelligently handle the Y2K
"wrap" using 2 digit displays which are industry specific.
Bottom line: the software publishers which are now under the Y2K gun are
publishers who chose to ignore the problem and/or expected customers to fork
over fresh money for upgrades to get the problem solved.
Earl
-----Original Message-----
From: Peter2150@xxxxxxx <Peter2150@xxxxxxx>
To: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
Cc: chris@xxxxxxxx <chris@xxxxxxxx>
Date: Thursday, July 16, 1998 1:13 PM
Subject: Re: CPR
>It is not a bug. It is simply the way all software reads dates. They are
|