Re: Strange Fortran version


Richard Maine wrote:
<john@xxxxxxxxxxxx> wrote:

1) DATA (A=123.55)

execution. Replace it with

DATA A/123.55/

I'm guessing you are
using it to mean "variable"). In any case, the variables in different
subroutines are different variables, even if they have the same name -
that doesn't make them even related.

The problem is that the variable (sorry for the 'element' confusion) is
declared in
a COMMON, so it is in fact common to several subroutines... And each of
the
routines has a DATA (A=123,44) statement...


2) ENTRY label

Entry points in SUBROUTINES - but using the same label in different
routines...

I don't recall seeing that one. If I'm understanding what you are
saying, I don't see how it would even figure out which one to use for a
given call, unless the code happens to depend on knowing exactly how the
linker in question works. Perhaps I misunderstand. You'll have to use a
unique name for each subroutine or entry point... which means you'll
havet o figure out which one each CALL is intended to refer to. I have
no idea how to do that other than by looking at what the code is doing
andseeing which one makes sense.

That's exactly my problem (and the compiler's complaint). The ENTRY
statement
appears in a number of SUBROUTINES (even in the same .for file), and
each
defines the same label.

3) A=B=C=0.

Chained assignment statements (a la C?)

Yes. That's just a non-standard syntax for

A = 0
B = 0
C = 0

Ok - that was the easiest one ;-)


4) SET=0.
IF (SET) ....

Use of a variable as boolean value? (also a la C?)

There are several variants of that one. I'd have to see what was in the
... and what the type of SET was. I'm assuming that SET here is REAL,
based on the clue of the assignment. In that case, if the ... is three
comma-separated statement labels, as in

IF (SET) 100, 200, 300

Ok... Yes, I remember that. But the compiler did complain. I'll try and
compile again.

The code is from the internet - the program is a raytracing program for
ionospheric
rays. http://cires.colorado.edu/~mjones/raytracing/3d-iono.75/

I haven't found another program that does a similar thing, and it would
be helpful
for my students at the university.

Thanks all!
John

.

Relevant Pages

  • Re: reference a vb.net windows form control from a module sub
    ... > application with a few subroutines in a separate module. ... > label or text box on the form. ... > a "Reference to a non-shared member requires an object ... error message. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Strange Fortran version
    ... Entry points in SUBROUTINES - but using the same label in different ... kenneth dot h dot fairfield ...
    (comp.lang.fortran)
  • reference a vb.net windows form control from a module sub
    ... application with a few subroutines in a separate module. ... label or text box on the form. ... a "Reference to a non-shared member requires an object ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Strange Fortran version
    ... "ENTRY lable" was common in some Fortran IV subroutines and probably ... Fortran compilers (many were written as a higher exercise in M.SC tasks ...
    (comp.lang.fortran)
  • Re: Subroutine calling a function?
    ... Your functions (and subroutines) are all external ones. ... External procedures were designed with separate compilation in mind. ... This implies that when compiling the code that invokes the ... the compiler can't look at the code ...
    (comp.lang.fortran)