Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!harrier.ukc.ac.uk!trh From: trh@ukc.ac.uk (T.R.Hopkins) Newsgroups: comp.lang.fortran Subject: Re: A Lint-like tool for fortran Message-ID: <3915@harrier.ukc.ac.uk> Date: 21 Feb 90 10:39:31 GMT References: <9080001@hpfcso.HP.COM> Reply-To: trh@ukc.ac.uk (T.R.Hopkins) Organization: Computing Lab, University of Kent at Canterbury, UK. Lines: 44 In article <9080001@hpfcso.HP.COM> mike@hpfcso.HP.COM (Mike McNelly) writes: >Hewlett Packard HP-UX machines have a utility, flint, which does what you >want. It is proprietary. > >Mike McNelly >mike%hpfcla@hplabs.hp.com There is a proprietary s/ware product called flint which provides ANSI standard (and many other portability and stylistic) warnings, complexity measures, call trees, basic block coverage etc. It is very fast and available on a lot of machines. Contact address Les Hatton Programming Research Ltd Kings Avenue House Kings Avenue New Malden Surrey, UK +44 1 942 9242 There is a Toolpack utility for standard checking which consists of a sequence of tools - a lexer, a parser, a semantic checker and a inter-program unit checker. The problem with it is that if one of first tools fails (e.g., you have VAX extensions in your source) then you can't go any further down the chain. FORCHK (available form Leiden University) is a Fortran 77 version of the old PFORT -- i.e., it does ANSI Fortran 77 standard checking. We have a copy of this but I haven't had time to really pound it. First impressions are good though. Tim -- Tim Hopkins, { trh@ukc.ac.uk Computing Laboratory, trh%ukc@cs.ucl.ac.uk University of Kent, na.hopkins@score.stanford.edu } Canterbury CT2 7NF, Kent, UK.