[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Y2K for the railway industry

Subject: Re: Y2K for the railway industry
From: "BHP" <saxon.ian.ia@bhp.com.au>
Date: 15 Nov 1998 23:41:17 GMT
Newsgroups: aus.rail, misc.transport.rail.australia-nz
Organization: BHP
References: <71tp84$2ho$1@nnrp1.dejanews.com> <72ko4o$sn$1@lios.apana.org.au>
Xref: news.mel.aone.net.au aus.rail:36163 misc.transport.rail.australia-nz:7731

Automatically putting 20 in front of the year when the TMS clock is set to
86 is what any good programmer would have coded when writing programs now. 
It is assumed that no one wants to go backwards in time.

Ian

> Interestingly, if the TMS clock is set to any year prior to '86', it
assumes
> it's next century and sets the year to '20xx', but if the year is '86' or
> higher, it assumes (correctly) that the year is '19xx'. That's definitely
a
> strange quirk...
> 
> Regards,
> 
> Craig.
> --

References:
- Re: Y2K for the railway industry
  - From: craigd@lios.apana.org.au (C. Dewick)

Prev by Date: Re: MCC
Next by Date: Re: Just trying
Prev by thread: Re: Y2K for the railway industry
Next by thread: Re: Y2K for the railway industry
Index(es):
- Date
- Thread