Starting in 1998, I began receiving frequent enquiries as to whether
Fdate is Y2K-compliant.
The short answer is:
The long answer is:
- Yes. Fdate is Y2K compliant.
- Fdate's whole purpose in life, from the very beginning, was to do
date handling and date arithmetic CORRECTLY. So Fdate has been Y2K
compliant from the very first version.
Note, however, that some of Fdate's functions (e.g. retrieving the
current date from the system clock, retrieving a file's
modification date) are dependent on the underlying platform
(hardware and operating system), which may or may not be Y2K
compliant. Fdate can be relied upon to behave in a Y2K-compliant
manner only if its underlying platform is Y2K compliant.
Fdate's YEAR-ASSUMPTION ALGORITHM, AND Y2K
Prior to version 9.8 Fdate used a "fixed" date-windowing algorithm
for dealing with 2-digit years.
if YY is greater than 20, then CC (the century) = 19
if YY is less than or equal 20, then CC = 20
This algorithm (like most Y2K date-windowing algorithms) is
date-dependent on the turn of the century that will occur in 2000.
I have developed a new algorithm that is independent of that date,
and it is the primary reason for the release of Fdate version 9.8
in March 1999. Starting with version 9.8 Fdate uses a "floating"
date-windowing algorithm for dealing with 2-digit years. This
algorithm will NEVER expire.
see TOPIC Fdate's Century-Assumption Algorithm