🚀 go-pugleaf

Well, it appears that a true lint doesn't exist. Here's the notes that've
come in today. It's unanimous for "cc -Wall file.c", for better or worse.

Maybe release 3.0...

Thanks for the responses,

Greg Ferguson
rtmd30@email.sps.mot.com
gregf@shaman.sps.mot.com

-------[attachments follow]-----------

From uunet!CS.YALE.EDU!rochberg-david Thu Jul 23 11:46:31 1992

cc with the -Wall option is a fairly effective lint replacement.

Apologies if you've heard this already and are looking for the real
thing.

					-david
-------------------------------------------------------
From: Brian Glaeske <uunet!cs.uwp.edu!glaeske>

Compile your programs with the -Wall option.  GNU C does it's own checking.

Brian Glaeske
-- 
 -  /|                        glaeske@cs.uwp.edu  		[Internet]
  o.O`   --Ooop ACK!!         ..!uunet!plains!gehenna!brian 	[NeXT UUCP]
=(___)=
   U    "Bill the Cat for Prez in '92"
-------------------------------------------------------

From uunet!PSUVM.PSU.EDU!MKK2 Thu Jul 23 13:45:44 1992

Ah!  The monthly "Where's lint?" question.

I don't want to get into the argument---I am not expert in these matters.
However, the usual answer is (a) use the -Wall option on the gnu C
compiler, it does most of what lint does, and (b) if you are porting software
to another platform (which is what lint helps with above and beyone -Wall)
then use the lint on the other platform.

cheers
-------------------------------------------------------

From: N Tomczak-Jaegermann <uunet!vega.math.ualberta.ca!ntomczak>

Try first -Wall flat to your compiler and study docs for other
-W... flags which are not covered by -Wall.   This has both
advantages and disadvantages over lint, but this is all what
you are going to get, I am afraid.  At least as far as I know.

   Michal Jaegermann
   ntomczak@vega.math.ualberta.ca