Re: Structure of large link libraries in f95

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.
.

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: a very simplistic example of a perl module
    ... I would like to move some subroutines into a module, perlmod and other ... tutorials online seem to provide too much detail. ... $ cat Foo.pm ...
    (comp.lang.perl.misc)