Re: use module to pass data between procedures

"Mike" <SulfateIon@[EMAIL PROTECTED]
> wrote in message 
news:67e34b00-05c2-4a08-8735-1eb6f1d8f1ad@[EMAIL PROTECTED]
>thank you for your explanation.
>So I need to check every time, if I use a module to pass the data
>between procedures.  It's quite troublesome.
>I have read some Fortran book which saids that common is obselete.
>But I think if I use named common to pass these data between
>procedures (I mean FCN), then I don't have to worry about if these
>data are declared twice.  Am I right?

Well sort of, but modules are so much better than common blocks IMO.
Historically bad common block usage has been the source of many problems.
I 
have seen code where different include files have the same named common 
block but with different variable names causing, at minimum, confusion to 
the person assigned to debug a problem
(ie me!).
However if you are working with, or upgrading, old code then yes, with 
modules you will have to check for duplicate declarations, but the
compiler 
will identify these for you (as shown in your first post).

Personally I would also put the FCN routine in the shared_data module, 
anything that needs to call FCN then has a "use shared_data" statement and

voila gets access to array y *and* FCN at the same time.

Les