Tech and Academic things for Chianshin

Friday, February 10, 2006

Google Groups : comp.lang.fortran

This is some information from the discussing group of fortran.

Now the main problem of me is just implicit declaration of the varibales. So using f77's warning message is eough.

Google Groups : comp.lang.fortran: "'Russell J. Allgor' wrote:

> If anyone has any other favorite lint checkers that aren't
> mentioned in the FAQ, I'd appreciate the information. We currently
> use the HP lintfor tool, and ftnchek.

See Fortran Journal, Jul/Aug 94 for a review of FLINT static F77 code
analyzer.

Fortran Forum Sept 94 (and earlier) lists FLINT and other F77 static
analysis tools.

Ref: http://www.fortran.com/fortran

The following are the main F77 code analysis tools listed in FForum:

1. FLINT 'detects inconsistencies in common blocks and in argument
lists, non-portable code, and usage of variables. Produces a call tree
and a symbol table. A version for C language is also available.
Single-user license $3900 [for UNIX or VMS;] also available for many
other hardware platforms. Information Processing Techniques Corp;
1096 E. Meadow Cir; Palo Alto CA 94304; (415) 494-7500; FAX 494-2758'

2. 'ftncheck' which you have ('mon...@mary.fordham.edu')

3. 'ForCheck' -- email: 'for...@rullf2.leidenuniv.nl' -- also supports
some F90 features; available for PC (price: 1050 dfl), VMS, Primos,
MVS, etc.

4. At a different level, 'VAST/77to90' does a lot of checking and code
restructuring while converting from F77 to F90. From Pacific-Sierra
Resea"

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]



<< Home