> Don't you think it will be simpler just to raise the base year to say 1954. > Who need a date back to 1904 at year 2032? :)) would be nice. but then everyone will be complaining "oh... in 2082... this thing screws up!".. no difference. the comment which i wanted to get across was that sure, there may be limitations on the date types right now - but as long as you stick to the API's, and dont become so dependant on the implementation, when the updated ROMS come out (in 2031) - no code has to change. most OO programmers call this technique "informaiton hiding".. just use the damn thing.. dont care as to how it is implemented. (all programs have bugs.. thats just a fact of life).. y2k has formed, because people were dependant on having 2 digits. az. -- Aaron Ardiri Lecturer http://www.hig.se/~ardiri/ University-College i G�vle mailto:[EMAIL PROTECTED] SE 801 76 G�vle SWEDEN Tel: +46 26 64 87 38 Fax: +46 26 64 87 88 Mob: +46 70 352 8192 A/H: +46 26 10 16 11
- RE: y2k bug inherent in DateType? Aaron Ardiri
- RE: y2k bug inherent in DateType? Alan Johnson
- Re: y2k bug inherent in DateType? Chuck Christensen
- Re: y2k bug inherent in DateType? Steve Patt
- RE: y2k bug inherent in DateType? Shaolin Hu
- Re: y2k bug inherent in DateType? Marcel Guldemond
- Re: y2k bug inherent in DateType? Alan Pinstein
- Re: y2k bug inherent in DateType? Steve Patt
- Re: y2k bug inherent in DateType? Kenneth Albanowski
- RE: y2k bug inherent in DateType? Tom Zerucha
- Re: y2k bug inherent in DateType? Aaron Ardiri
- Re: y2k bug inherent in DateType? Aaron Ardiri
- y2k bug inherent in DateType? Michael Hutchens
- Re: y2k bug inherent in DateType? Aaron Ardiri
- Re: y2k bug inherent in DateType? krollin
- Re: y2k bug inherent in DateType? Michael S. Davis
- Re: y2k bug inherent in DateType? Aaron Ardiri
- Re: y2k bug inherent in DateType? Aaron Ardiri
- Re: y2k bug inherent in DateType? krollin
- Re: y2k bug inherent in DateType? Laurence Lundblade
- Re: y2k bug inherent in DateType? Kenneth Albanowski
