Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!purdue!bu.edu!mirror!necntc!necssd!harrison
From: harrison@necssd.NEC.COM (Mark Harrison)
Newsgroups: comp.lang.c
Subject: Re: problems/risks due to programming language
Summary: Gimpel PC-Lint and Flexe-Lint can help
Message-ID: <248@necssd.NEC.COM>
Date: 6 Mar 90 14:24:23 GMT
References: <1597@awdprime.UUCP> <8133@hubcap.clemson.edu> <2903@goanna.oz.au> <18033@rpp386.cactus.org>
Organization: NEC America Inc. SSD, Irving, TX
Lines: 23

In article <2905@goanna.oz.au>, ok@goanna.oz.au (Richard O'keefe) writes:

> : defined.  That means that you can have a statement which you meant to have
> : in the if statement but isn't."  You know, something like
> :   if (a == b)
> :        bar(a);
> :        foo(a);
> :   a++;
> : Do you propose making an editor macro to handle ifs to prevent this?

You might look at Gimpel Software's PC-Lint and Flexe-Lint packages.  It will
warn you if your indenting does not match your curly braces, along with
dozens of other really useful warnings (printf args not matching fmt string,
etc.)

They advertise in Dr. Dobbs, Comp. Language, etc.  The two programs are the
same; PC-Lint runs on MS-DOS, Flexe-lint runs on Unix, VMS, CMS, Amiga,
Macintosh, and just about any other environment that supports K&R C.
-- 
------------------------------------------------------------------------
Mark Harrison				| (these opinions
harrison@necssd.NEC.COM			|  are my own, etc.)
{necntc, cs.utexas.edu}!necssd!harrison |