Letter: September bug

William Hudson
Wednesday 21 July 1999 23:02 BST
Comments

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Sir: Your forecast of additional millennium bug problems after 9 September 1999 (report, 19 July) is very unlikely to be realised. Speaking as a now geriatric former software writer I am 99.99 per cent certain that nothing of note will happen on or around that date.

The basis for your original concern surrounds the practice, when using fields of fixed width, to allow invalid values to represent the end of a sequence. In the 1970s, dates would have been of the form "ddmmyy", resulting in the familiar millennium bug problem: 1999 was of course not invalid, but sufficiently far in the future to convince most developers that their work could not possibly be in use by that date. However, the "end of file" sequence would be 999999, or the 99th day of the 99th month, 1999, not, as your article suggests, 090999.

WILLIAM HUDSON

Abingdon, Oxfordshire

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in