Re: Structure of large link libraries in f95

Charles Russell wrote:
Charles Russell wrote:

Richard E Maine wrote:


Compile your code and put it in a library the same way you do now. Then
make a module with nothing but interface blocks.



Things could be

automated, but I'm not a makefile guru.


On second thought, this might be pretty simple. List the subroutines in one makefile macro and the functions in another, cat each set, change all end statements in each set using sed, cat the two together and INCLUDE the resulting file. Make all library files prerequisites.

Having done that, am I likely to hit other problems related to f77 syntax or format? As you can tell, I am not ready to cross this bridge, only to reconnoitre.

This was a bit out of context. It refers to the "end subroutine" syntax problem, not to the use of explicit interfaces.
.

Relevant Pages

  • Re: Structure of large link libraries in f95
    ... make a module with nothing but interface blocks. ... List the subroutines in one makefile macro and the functions in another, cat each set, change all end statements in each set using sed, cat the two together and INCLUDE the resulting file. ... Make all library files prerequisites. ...
    (comp.lang.fortran)
  • Re: Structure of large link libraries in f95
    ... tools to help in automatically reading the source and making appropriate ... interface blocks only infrequently, ... List the subroutines in one makefile macro and the functions in another, cat each set, change all end statements in each set using sed, cat the two together and INCLUDE the resulting file in the module. ... Make all library files prerequisites. ...
    (comp.lang.fortran)
  • Re: interface blocks
    ... Lynn McGuire wrote: ... > I have about 3500 subroutines with 400,000 lines of f66/f77 that I am ... interface blocks, and Michael Metcalf has a free program for that does ... both the approriate keyword and the procedure name." ...
    (comp.lang.fortran)
  • Fortran module in a library
    ... I have dozens of subroutines in a module file, ... provide generic names via interface blocks. ... avoid unintentional code changes and subsequent time-consuming ...
    (comp.lang.fortran)
  • get "undefined reference" with routines contained in a module
    ... END SUBROUTINE func1 ... If I compile/link both files at the same time, ... Do I have to use interface blocks to reach my goal although I used internal functions/subroutines? ... The subroutines don't contain user-defined data types, etc which would need interface blocks. ...
    (comp.lang.fortran)