Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
I was a FORT IV man many years ago. All I can remember now is you had to leave some sort of margin for optional line numbers, and six-character variable names. I think.
I was a FORT IV man many years ago. All I can remember now is you had to leave some sort of margin for optional line numbers, and six-character variable names. I think.
and there were no block ifs in FORTRAN IV - You had to negate the condition and use a GOTO to a label past the code subject to the IF
First six characters on a line are reserved for a numeric label:
1000 FORMAT(1X, 80A1)
sort of thing.
Character 7 is the extender, which joins the current line onto the line preceding it...
Then characters 8 to 71 hold the code....
Finally characters 72 to 80 have the card sequence number which is mighty handy if you drop the deck of cards and the rubber band breaks...
All of which is now bollocks, coz you can use the namby pamby freeform.
Real Programmers wrote
FORTRANINUPPERCASEWITHOUTANYSPACESCOZTHECOMPILERLI KEDITLIKETHAT
I haven't written a line of FORTRAN since 1991...
Talking about all this column alignment stuff, does anyone agree that python, despite its object-oriented slant, is a massive leap back into the dark ages with its reliance on column alignment for nesting of ifs?
I think it's vile, and I won't touch the language.
Comment