Remember the old chestnut of wave recompilation when USEing subroutines
contained in F90 modules. I need to revisit the problem, and have come up
with a possible make based solution that relies on automatic generation of
argument information from f90 source to produce seperate .interface files
that can be INCLUDEd in calling routines.
Before I fiddle around writing the Perl to do the generation of the
interface files, I wondered if anyone else knew of a tool that would parse
code and extract subroutine arguments and their associated declarations to
a separate file. A first cut would just need to spot things inside
SUBROUTINE xx () and variables declared with an INTENT, but a more general
one would have to match variable name tokens with their otherwise unmarked
declarations.
John
--
John Bray, Numerical Weather Prediction Tel: +44 (0) 1344 854035
Room 337 [log in to unmask]
The Met. Office http://www.met-office.gov.uk
London Road, Bracknell, RG12 2SZ, UK http://www.jrbray.org.uk
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|