Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?

To: Hawkmoon who wrote (5439)	4/10/1999 5:37:00 PM
From: David Eddy	Read Replies (1) \| Respond to of 9818

Ron - You must be a programmer, David. Since truncating date inputs in order to save memory space seems suspiciously similar to making Y2K the acronym for the Year 2000 programming fault. I haven't written code in 10+ years. And before I was a programmer I was abbreviating things... just like everyone else who doesn't want to write out Chernyshevsky or Dobrolyubov every time. Btw, did you ever follow the work that Bob Bemer Thanks for the softball... remind me to send you a referal fee. <g> I was more than involved in Bob Bemer's effort. He saw the Wall Street Journal story about me (8/25/95), was shocked to learn that the short date problem hadn't been solved & came out of retirement. To the best of my knowledge, his solution hasn't taken off either. - David

To: Hawkmoon who wrote (5439)	4/10/1999 6:33:00 PM
From: Jim	Read Replies (1) \| Respond to of 9818

You must be a programmer, David. Since truncating date inputs in order to save memory space seems suspiciously similar to making Y2K the acronym for the Year 2000 programming fault. Insignificant point, but when I was writing Cobol programs in the 1960's, I did not use two digit fields to save computer memory, but to save columns on punched cards. Also, I converted some of our current systems to ask for MMDDYYYY instead of MMDDYY and the data entry operators are complaining about having to enter 1999 or 2000 each time. I promised that after next January, we would change the data entry back to YY ie. 00,01 etc. for those applications that only have data entry for current + years. (remember, we use serial date storage so the dates are always stored correctly.)