> > --John (who long has said that while Unix provides the tools to handle >Y2K properly (Y2038 is another matter), it's still possible to produce >results which have Y2K problems by misusing the tools Unix provides. >Actually, I mostly said that about MacOS) >-- Well, Mac is going to UNIX. Does anyone want to lay a wager on whether there will, in 2035~8, still be systems compiled with the old "typedef unsigned long time_t" or "typedef long time_t" running? A more meaningful question would be as to whether anyone has heard of a time library that handles the various (known) epocs? That might be a fun project. Guess I ought to get on Google and look this up. # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org