Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: common bugs in C programs
Message-ID: <367@sixhub.UUCP>
Date: 1 Jan 90 19:02:15 GMT
References: <61500001@uicbert.eecs.uic.edu> <523@oglvee.UUCP>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 19

In article <523@oglvee.UUCP> norm@oglvee.UUCP (Norman Joseph) writes:
| From article <61500001@uicbert.eecs.uic.edu>, by damerla@uicbert.eecs.uic.edu:
| > 
| > I am compiling a list of syntax and logical errors I ever made while writing
| > C programs.  Some of these errors are very simple but hard to debug like typing
| > = in place of ==.  Till now I have compiled about 25 of them and any 
| > contributions to this list will be appreciated.

  When developing the IMP language from B, along with other changes I
used = for equality, := for assignment, and <> for not equal. This was
strongly influenced by the widespread use of Algol60 at that time, but
the people who helped me design changes agreed that these were
readability improvements. Oddly, the change from =+ to += never went in,
and the language is dead now.
-- 
	bill davidsen - sysop *IX BBS and Public Access UNIX
davidsen@sixhub.uucp		...!uunet!crdgw1!sixhub!davidsen

"Getting old is bad, but it beats the hell out of the alternative" -anon