Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!asuvax!ncar!unmvax!bbx!bbxsda!scott
From: scott@bbxsda.UUCP (Scott Amspoker)
Newsgroups: comp.lang.c
Subject: Re: Funny mistake
Message-ID: <1775@bbxsda.UUCP>
Date: 20 Mar 91 15:24:57 GMT
References: <1991Mar13.125034.2825@st-andy.uucp> <13337@helios.TAMU.EDU> <8148@rsiatl.Dixie.Com> <15481@smoke.brl.mil> <775@camco.Celestial.COM> <525@bria>
Reply-To: scott@bbxsda.UUCP (Scott Amspoker)
Organization: Basis International,  Albuquerque, NM
Lines: 24

In article <525@bria> uunet!bria!mike writes:
>[ in regards to the expression "if (a = b)" instead of "if (a == b)" ]
>
>Think *lint*.  IMHO, there is nothing we need less than a compiler spitting
>out more useless verbage.

The only problem with that is that many PC based C compilers don't include
a lint program.  It makes sense that the programmer at least have the option
of enabling various warning messages.  Strangely enough, I once comitted
the exact opposite mistake.  I had a C statement like this:

	    i == j;

The compiler (bless its little heart) gave me the warning:

	"code has no effect"


-- 
Scott Amspoker                       | Touch the peripheral convex of every
Basis International, Albuquerque, NM | kind, then various kinds of blaming
(505) 345-5232                       | sound can be sent forth.
unmvax.cs.unm.edu!bbx!bbxsda!scott   |    - Instructions for a little box that
                                     |      blurts out obscenities.