TIP: Click on subject to list as thread! ANSI
echo: maximus
to: SCOTT DUDLEY
from: NIEL UYS
date: 1997-10-12 09:53:00
subject: Year 2000

Scott Dudley wrote in a message to Gerry Danen:
 GM>> max is y2k compatible. for dates, using "100" as the year means
 GM>> "2000".. "143" = "2043"
 GD> That's not compliance, that's a work-around. Compliance means 4-digit
 GD> years and not some interpretation by the software.
 SD> Why does compliance mean 4-digit years?  If Maximus were to support
 SD> 2-digit years properly ("01/14/00 = January 14, 2000"), how on
 SD> earth could that not be compliance?
Hi Scott, the industry says 4 digits is compliance, not 2. The problem with 
your reasoning is that if everyone follows their own nose (As to say), then 
we'll have multiple interprtations on the subject, which could lead to 
confusion amongst programmers in future. I am not bashing you, merely stating 
the possible problem that might appear. I work for IBM and are involved in 
the y2k problem in application software...
 SD> Furthermore, suppose that Maximus does use four-digit years, but
 SD> assume that it uses dashes instead of slashes to separate the
 SD> components.  I suppose that this would make it "incompliant" too?
 SD> As long as date handling is internally consistent and an intuitive
 SD> way to do things, who cares what the rest of the industry does?
Exactly my point above. I think we have to care, not what the industry does, 
but to make sure we all follow the same rules, otherwise chaos will exist. 
Maybe I sound like a priest, but one has to think about it. Your program, Max 
and Max/2 are used around the globe, not only by sysops, but by corporate 
companies, like IBM and if it is not 100% compliant, it will be replaced with 
something that is...fact!
 SD> I agree that "01/03/103" is awkward and unintuitive, but I fail to
 SD> see why we *must* replace it with four-digit years in cases when a
 SD> properly-interpreted two-digit year is unambiguous and works just
 SD> as well.
 SD> Obviously, for birthdates, a four-digit year is the way to go.  On
 SD> the other hand, do you think there is really any point in
 SD> cluttering up the file area listings or the current date display
 SD> with four-digit dates?
As a sysop, the above will work of course, but it would be y2k 
mpliant...:-)
Never-the-less, your Max is still the best BBS package around...till y2k :-)
Keep Well,
           Niel 
--- timEd/2 1.10
---------------
* Origin: Goldfields EchoLink CBCS * Joh'burg (5:7101/3)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.