Anonymous user
User talk:Wherrera: Difference between revisions
added some clarification concerning program statement columns.
mNo edit summary |
(added some clarification concerning program statement columns.) |
||
Line 24:
Found the problem: I had a floating point precision error. Thanks for checking.
-- [[User:Wherrera|Wherrera]] 23:54, 15 November 2019 (UTC)
== comments about source statements that can start in column one ==
Concerning the Rosetta Code task (''Long literals, with continuations'') regarding (source) statements that can start in column other then one was meant for those computer programming languages that have column dependencies, some of which are (or used to be) such languages like:
:* BASIC (various flavors) some columns were meant for statement numbers
:* COBOL
:* older versions/flavors of FORTRAN (note the uppercase spelling) when columns 1 --> 5 were meant for statement numbers, and column 6 was for continuation), nowadays, it seems that most Fortrans are free-form
:* PL/I (used to) optionally reserve column one for carriage control, and statements started in column two
:* some assembler languages, where tokens starting in column one were reserved for statement labels
:* other computer languages that used a non-blank character in column seventy-two for continuation
:* other computer languages that used columns 73 --> 80 for sequencing numbers
:* ... and I'm sure many other (possibly older if not ancient) languages had column specifications for (statement) start and/or continuation
It would be interesting to learn (and know of) these old restrictions/specifications for non-free form computer programming languages. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 05:28, 24 March 2020 (UTC)
| |||