On Wed, 28 Apr 1999, Jose Angel Amador Fundora wrote:
> I am going to quote James Dugal, N5KNX, on what he published about
> this matter on JNOS documentation. For JNOS he chose the following
> representation: any year larger than 50 is 19xx, say, 99 means 1999,
> and any number smaller than 50 is 20xx, say 00 is 2000. The idea
> behind this is that JNOS 1.11 would be so archaic in year 2050 that
> nobody would be using it. Seems a smart solution to me.
I have used the same method in software I've written,
but it's still only a temporary solution
because it just moves the problem 50 years.
I agree it's likely to be unused by then,
except that when I look at my CP/M system......
The scheme I'm getting around to implementing
writes the current date to a file somewhere.
This file can be per application, or system wide.
It could also be the year only, stored in CMOS.
When starting, the application reads the date in the file
and picks a 100 year window based on that.
It doesn't have to be 50 years either way,
since each application has its own idea
of how far in each direction it needs to see.
On termination, the application writes the current date again.
This way, the base year moves along with the use of the computer
(unless you start an application after its idea of the end of the window,
but not using a computer for numerous years may make
the date somewhat less critical :-) ).
The code to do all this would be fairly trivial.
Kevin
