Talk:Fortran: Difference between revisions
Jump to navigation
Jump to search
imported>Paul Wormer (New page: {{subpages}}) |
imported>Howard C. Berkowitz (→FORTRAN (I): new section) |
||
| Line 1: | Line 1: | ||
{{subpages}} | {{subpages}} | ||
== FORTRAN (I) == | |||
While it's unfortunately in storage, one of my proud possessions is a FORTRAN manual for the IBM 709. It isn't called FORTRAN I because no one had yet contemplated a II. No, I never wrote for a 709; the closest I got was converting IBM 7094 code to run on the UNIVAC 1108. | |||
There are some interesting, obsolete features. The FREQUENCY statement preceded optimizing compilers, and indeed PRAGMA or other human-judgment features in other languages. FREQUENCY follows an IF statement, and expresses the programmer's expectation of the frequency with which each branch will be taken. The compiler would use this information to order the comparisons in machine code. [[User:Howard C. Berkowitz|Howard C. Berkowitz]] 17:20, 3 August 2009 (UTC) | |||
Revision as of 11:21, 3 August 2009
FORTRAN (I)
While it's unfortunately in storage, one of my proud possessions is a FORTRAN manual for the IBM 709. It isn't called FORTRAN I because no one had yet contemplated a II. No, I never wrote for a 709; the closest I got was converting IBM 7094 code to run on the UNIVAC 1108.
There are some interesting, obsolete features. The FREQUENCY statement preceded optimizing compilers, and indeed PRAGMA or other human-judgment features in other languages. FREQUENCY follows an IF statement, and expresses the programmer's expectation of the frequency with which each branch will be taken. The compiler would use this information to order the comparisons in machine code. Howard C. Berkowitz 17:20, 3 August 2009 (UTC)