Re: Strange Fortran version

I've seen all of these statement types before.

"ENTRY lable" was common in some Fortran IV subroutines and probably
F66 versions.
It defines an alternative entry point (a different same for the same
subroutine) on subroutines that were used in more than one way, usually
to avoid reinitialising something only wanted on a first entry (e.g.
seeded random number generator) or to use one of several alternative
initial code paragraphs before a common later section of code was
branched to in order to complete the general nature of the function
desired.

The "A=B=C=0." chained assignment I've seen with university-built
Fortran compilers (many were written as a higher exercise in M.SC tasks
and sometimes then used at lower levels by other students, and possibly
research students who sought advice on computational work. I remember
this was commonly recommended as a change to the Fortran specifations,
to make intentions clear.
I think is was valid in Pascal and some forms of Basic.

I cannot recall seeing any use of a computational IF that used a real
variable but then later tested against integer values, but in
principal, the integer test values should be converted to float in the
compilation (since float is the higher form) and the intepretation
would be correct (for those days).
..
Terence Wright

.

Relevant Pages

  • Re: Help! simple compile question
    ... Actually "common" blocks are considered to be obsolete in Fortran 95, use a global module is a better choice. ... Using Modules containing subroutines is another way to do this, or if you want, you can build a library and use the library instead. ... arrange the compilation. ... Apart from the fact that f77 is valid f95, the INCLUDE statement wasn't part of the fortran standard until f90. ...
    (comp.lang.fortran)
  • Re: Program organization
    ... There is a lot of good and useful advice in both editions, even though Steve McConnell has a decidedly negative view of Fortran in the 1st edition and the examples in the 2nd edition are heavily oriented toward the Microsoft Visual Studio languages. ... and all other files define one of the subroutines. ... Modular decomposition is a very powerful and effective practice in software engineering. ... You talk about two separate issues here, global data and source code file organization. ...
    (comp.lang.fortran)
  • Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
    ... Mandated backward compatibility is insuring fortran survival despite ... I fully agree with your comments about COMMON - used without tricks ... and if it isn't a nightmare for the compiler writer, ... Fortran programming - I never felt a real need for it - and I wrote ...
    (comp.lang.fortran)
  • Re: When will this ng come to accept that Fortran needs to go "back to the future" ?
    ... Mandated backward compatibility is insuring fortran survival despite ... I fully agree with your comments about COMMON - used without tricks ... Fortran programming - I never felt a real need for it - and I wrote ... But I would support it if it can be done as a clean extension from the ...
    (comp.lang.fortran)
  • Re: keyword capitalization -- current practice
    ... with regards to capitalizing keywords in Fortran. ... I'm not convinced that you will find a single most common style. ... I've also seen styles where people capitalize the first letter of ...
    (comp.lang.fortran)