Lloyd Fuller wrote: >Actually in some products quite a lot.
Some other applications like your example: 1. Astronomy: (Calculating position/movements of space things from x year/month/day/etc to y year/etc...) 2. Statistics and Mathematics: Census processing of population of people, animals, disease growth, etc. Only for really bored students. ;-D 3. Deeds registration: Registration of property. 4. Laws: Writing down laws and refering to year when past laws were made. >Internal dates went from 1/1/1600 to a time VERY long in the future (year >10000 something). It depends on language used. >In fact, after discussion we even implemented the leap year calendar in the >past by using negative dates. In what format? (COBOL, Assembler, other?) Just curious if you dont mind, please? Kees Vernooij wrote: >If I only had a Euro for each program that has this code and will not live >until 2100... From your industry, you probably know that Boeing was already implementing Y2K fixes since about 1990 [1] due to long ordering period of about 12 years and more of aeroplanes from various clients. Groete / Greetings Elardus Engelbrecht [1] - I can't remember the exact year but it was certainly in those [ flying ;-D ] times. I would be grateful if someone can post a source confirming it. :-) I warned my management in around 1996 about the upcoming Y2K monster and I used the Boeing example as part of my motivation. But as you probably guessed it, the management got active around 1998 and then only because IBM was getting paranoid ( shame! ;-D ) about that undying Y2K monster. ;-) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
