Re: Subroutine Argument Checking
From: Michael Metcalf (michael.metcalf_at_t-online.de)
Date: 06/10/04
- Next message: David Fumento: "Re: Valgrind work with Intel Fortran/C++"
- Previous message: *** Hendrickson: "Re: qsort and arbitrary types"
- In reply to: beliavsky_at_aol.com: "Re: Subroutine Argument Checking"
- Next in thread: Hans-Bernhard Broeker: "Re: Subroutine Argument Checking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 10 Jun 2004 17:39:46 +0100
"beliavsky@aol.com" <beliavsky@127.0.0.1:7501> wrote in message
news:40c87c10$1_1@127.0.0.1...
>
> Arjen Markus <arjen.markus@wldelft.nl> wrote:
> >
> >Well, you would define the interface in a module - no need for the
> >source to be there! That way you get the advantages of Fortran 90 and
> >still use old stuff.
>
> Thanks for the good suggestion. I think the nag_mkintf95 interface builder
> of Nagware described at
http://www.nag.co.uk/nagware/nq/f95_description.asp
> is a tool to do this. For small amounts of code it is not difficult to do
> manually.
>
The convert.f90 tool also has an option to create a module full of interface
blocks from a FORTRAN 77 source file. You have to remember that the end
lines require the addition of a keyword; the tools adds both the approriate
keyword and the procedure name.
Regards,
Mike Metcalf
- Next message: David Fumento: "Re: Valgrind work with Intel Fortran/C++"
- Previous message: *** Hendrickson: "Re: qsort and arbitrary types"
- In reply to: beliavsky_at_aol.com: "Re: Subroutine Argument Checking"
- Next in thread: Hans-Bernhard Broeker: "Re: Subroutine Argument Checking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]