Re: FVWM: fvwm and the year 2000

From: Randy J. Ray <rjray_at_uswest.com>
Date: Sat, 12 Apr 1997 12:15:34 -0600

> >>>>> Ronald A Slusser writes:
>
> Ron> Is fvwm year 2000 compliant?
>
> I *knew* somebody would ask this... Well, in Unix time is measured in
> seconds since Epoch (Jan 1, 1970, midnight). 32 bit integers will run
> out in 2038 or so, so you ought to have bought a 64 bit machine by
> then :-)
>
> The year-2000 problem doesn't arise because there is no place where
> times are stored as a two-digit year value.

More to the point, fvwm is 2K compliant because no *calculations* are done on
dates that may have been stored in abbreviated format (Year 2K worries are
really big in the tele-coms these days).

>From my brief look at the source, the only places I see time being noted are
timestamps on events and on packets sent to modules. All of these times are
being recorded and transmitted as raw values returned from the C library, so
there should be no Year 2K problems in fvwm.

Randy
--
===============================================================================
Randy J. Ray -- U S WEST Technologies IAD/CSS/DPDS         Phone: (303)595-2869
                Denver, CO                                     rjray_at_uswest.com
"It's not denial. I'm just very selective about the reality I accept." --Calvin
===============================================================================
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Sat Apr 12 1997 - 13:16:22 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:00 BST