Friedrich Hertweck wrote:
>
> Well, it is not that simple with Cray F90 on the CRAY T3E. I would be
> interested to learn which Cray Compiler you use.
It is Cray CF90 Version 3.3.0.0
> That certainly is a problem. I would like some compiler implementation
> guidelines that require a compiler to have a mode in which the module
> interface information is kept in a *.mod file, while the corresponding
> object code is in a *.o file. In addition the facility should be augmented
> with a tool that
> (a) collects the interface-relevant information from a module and generates a
> "dummy" module, and
> (b) is able to compare two modules if they have identical interfaces.
> Note that this needs no alteration to the F95 standard, but it would greatly
> help the users. I personally feel that using extra interface declarations or
> procedure arguments are not desirable(the latter are fine when one wants to
> introduce various other procedures into a procedure).
Well, that would be nice. However, as already mentioned in the
discussion
other possibilities exist. Unfortunately, none of the proposed solutions
appears to be both legal F95, and satisfactory.
What is needed for independent module compilation is something
comparable
to the C header files.
Cheers,
Jörg
--
Dr.-Ing. Joerg Stiller, Dozent fuer Geo- und Magnetofluiddynamik
----------------------------------------------------------------
Technische Universitaet Dresden TEL : (0351) 463 - 8328
Institut f. Luft- und Raumfahrtechnik FAX : (0351) 463 - 8087
D-1062 Dresden [log in to unmask]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|