In message , at 11:21:09 on Tue, 5
Jan 2016, Peter CS remarked:

During a particularly wearisome Y2K fix job one of my team remarked that
we'd better allow for 5-digit years or we'd have to do the whole thing
again in 8000 years' time.

Roll on 2038, or have they fixed that yet?
--
Roland Perry

In message , at 23:29:07 on Tue, 5 Jan 2016,
Mizter T remarked:

The free travel ended at 0430 1st Jan and there weren't any reports of
problems yesterday.

That's a good point. I was expecting the free travel to have been all
day on the 1st.

Why? It's been 2345 NYE to 0430 NYD for years and years and years.

With the railway day ending at 4.30am I'd expect that to be called a New
Years Eve free travel period, not a NYD one.
--
Roland Perry

On 05/01/2016 19:34, wrote:
In article , d () wrote:


In a back end system certainly. In a smartcard with perhaps only a
few KB of RAM possibly not.

The time when dates had to be so compressed passed before the advent of
smartcards, believe me.


Not true - when you are dealing with billions of transactions and/or
millions of smart cards whose cost is proportionate to the storage on
them there is still pressure to minimise the space that data occupies

In message
-sept
ember.org, at 23:52:54 on Mon, 4 Jan 2016, Recliner
remarked:

Y2K type bugs date from software designed 40 or more years ago

Here's another I came across by chance today:

http://www.theregister.co.uk/2012/03...day_confirmed/
--
Roland Perry

Roland Perry wrote:
In message
-sept
ember.org, at 23:52:54 on Mon, 4 Jan 2016, Recliner
remarked:

Y2K type bugs date from software designed 40 or more years ago

Here's another I came across by chance today:

http://www.theregister.co.uk/2012/03...day_confirmed/

Wonderful! I'm pretty sure that even my distinctly amateurish code does
date checks in a smarter way than that (just subtract a date from today and
see if the answer is greater than 365 -- the system clock at least should
know all about leap years).

Roland Perry wrote:
In message , at 23:29:07 on Tue, 5 Jan
2016, Mizter T remarked:

The free travel ended at 0430 1st Jan and there weren't any
reports of problems yesterday.

That's a good point. I was expecting the free travel to have been
all day on the 1st.

Why? It's been 2345 NYE to 0430 NYD for years and years and years.

With the railway day ending at 4.30am I'd expect that to be called a
New Years Eve free travel period, not a NYD one.

It was referred to as free travel on or for NYE by (for example) TfL,
Metro, Evening Standard, Time Out, and the BBC - most media (as is the
modern way) copying from TfL's Press Release. Where please did you see
it called NYD free travel?

--
Robin
reply to address is (meant to be) valid

In message , at 10:50:04 on Wed, 6 Jan 2016,
Robin remarked:
Roland Perry wrote:
In message , at 23:29:07 on Tue, 5 Jan
2016, Mizter T remarked:

The free travel ended at 0430 1st Jan and there weren't any
reports of problems yesterday.

That's a good point. I was expecting the free travel to have been
all day on the 1st.

Why? It's been 2345 NYE to 0430 NYD for years and years and years.

With the railway day ending at 4.30am I'd expect that to be called a
New Years Eve free travel period, not a NYD one.

It was referred to as free travel on or for NYE by (for example) TfL,
Metro, Evening Standard, Time Out, and the BBC - most media (as is the
modern way) copying from TfL's Press Release. Where please did you see
it called NYD free travel?


Recliner said: "there was also the normal New Year's free travel"

OK, no "Eve" or "Day", but in my mind if defaults to the latter if not
mentioned.
--
Roland Perry

On Wed, 6 Jan 2016 11:56:56 +0000, Roland Perry
wrote:

In message , at 10:50:04 on Wed, 6 Jan 2016,
Robin remarked:
Roland Perry wrote:
In message , at 23:29:07 on Tue, 5 Jan
2016, Mizter T remarked:

The free travel ended at 0430 1st Jan and there weren't any
reports of problems yesterday.

That's a good point. I was expecting the free travel to have been
all day on the 1st.

Why? It's been 2345 NYE to 0430 NYD for years and years and years.

With the railway day ending at 4.30am I'd expect that to be called a
New Years Eve free travel period, not a NYD one.

It was referred to as free travel on or for NYE by (for example) TfL,
Metro, Evening Standard, Time Out, and the BBC - most media (as is the
modern way) copying from TfL's Press Release. Where please did you see
it called NYD free travel?


Recliner said: "there was also the normal New Year's free travel"

OK, no "Eve" or "Day", but in my mind if defaults to the latter if not
mentioned.

I did say "normal", meaning the same as in previous years, which have
never given free travel all day on the 1st of January. I assumed
people in u.t.l already knew that, and I didn't need to provide the
full terms and conditions.

In article , (Someone
Somewhere) wrote:

On 05/01/2016 19:34, wrote:
In article , d ()
wrote:

In a back end system certainly. In a smartcard with perhaps only a
few KB of RAM possibly not.

The time when dates had to be so compressed passed before the advent of
smartcards, believe me.

Not true - when you are dealing with billions of transactions and/or
millions of smart cards whose cost is proportionate to the storage on
them there is still pressure to minimise the space that data occupies

Not to that extent. They learnt something from Y2K.

--
Colin Rosenstiel

On 06/01/2016 15:01, wrote:
In article , (Someone
Somewhere) wrote:

On 05/01/2016 19:34, wrote:
In article , d ()
wrote:


The time when dates had to be so compressed passed before the advent of
smartcards, believe me.

Not true - when you are dealing with billions of transactions and/or
millions of smart cards whose cost is proportionate to the storage on
them there is still pressure to minimise the space that data occupies

Not to that extent. They learnt something from Y2K.

As it's panto season "oh no they didn't"