|File Search||Catalog||Content Search|
Unlike syntax errors, semantic errors are legal in the Fortran language but are wasteful or may cause incorrect operation. For example, variables which are never used may indicate some omission in the program; uninitialized variables contain garbage which may cause incorrect results to be calculated; and variables which are not declared may not have the intended type.
ftnchek can also be used to provide call-trees, cross-reference of subprogram calls and COMMON blocks usage, source listings, symbol tables and other things you might find useful when debugging a Fortran program.
README file for ftnchek version 3.3 Author: Robert Moniot Fordham University New York, NY 10023 USA Telephone: (212) 636-6311 URL: http://www.dsm.fordham.edu/~moniot Date: November 3, 2004 Ftnchek (short for Fortran checker) is designed to detect certain errors in a Fortran program that a compiler usually does not. Ftnchek is not primarily intended to detect syntax errors. Its purpos more»
ftncheck for Debian ------------------- ftnchek is a static analyser which checks Fortran source for correctness. It currently supports Fortran 77 and some aspects of Fortran 90 and 95. It is intended to improve on the error detection facilities of compilers, identifying problems which are either hard to catch and constructs which (while strictly legal) are likely to indicate an error. ftnchek more»
ftnchek FAQ This is a very preliminary FAQ. Originally written February 28, 1999. Slightly updated September 22, 2000 and August 23, 2002. Q1) Where can I get the latest version of ftnchek? Q2) Are there any plans for ftnchek to support Fortran 90? Q3) What other Fortran syntax checkers are there? Q4) Why is ftnchek not spelled ftncheck? Q5) What are some sources of Fortran informat more»
DCL2INC(1) DCL2INC(1) NAME dcl2inc - post more»
FTNCHEK 3.3(1) FTNCHEK 3.3(1) NAME ftnchek - Fortra more»
ftnchek (3.3.1-4) unstable; urgency=low * Force use of /usr/bin/awk. * Policy 3.7.3 (no changes more»
This package was debianised by Emilo C. Lopes <email@example.com>. It has since been adopted by Mark B more»