Hi,
When you read a record with FORTRAN, the read statement tells what the
numbers mean by the position of the numbers. I doubt that any of that
As I said, a date like "" wouldn't make any sense then,
unless you live in a world with only single digit months/days !
Of course this error
Hi,
The problem is/was that 9/9/99 was used as an exit code (esp for really old
text based data entry) eg:
Enter new date (enter 9/9/99 to exit program) :
Ah, now that's a plausible scenario. However, if I had been
the one who had contracted this programmer, I'd have him
executed on the spot.
EOF marker card was filled with 80 nines, since it was an 80 column
card. The code was being written when the date 9/9/99 was so far off
that everyone thought the program would be replaced by a more modern
technology before it bacame a problem. Using a 9's card to signify EOF
was standard
Hi,
EOF marker card was filled with 80 nines, since it was an 80 column
card. The code was being written when the date 9/9/99 was so far off
that everyone thought the program would be replaced by a more modern
technology before it bacame a problem. Using a 9's card to signify EOF
was standard
Hi,
Well, tomorrow is also a big day. They day of the nines card. I
remember using them to signify EOF or End Of File. So if your computer
programs stop tomorrow you will know why.
Ye gods, here comes another one...
This thing is just as fake as the Windows 2-digit one,
although not as
===
= NB: Over 50% of this message is QUOTED, please =
= be more selective when quoting text =
===
Actually this is a problem for some system..
When I wrote code back in the 60's and 70's using FORTRAN, we would read
the data, then check for 99 and if that apeared, we interpreted it
as End Of File and the program then processed the apropriate code to
stop reading the data and do the calculations and print the report.
When you
