Newsgroups: comp.lang.dylan
From: cyber_surfer@wildcard.demon.co.uk (Cyber Surfer)
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!europa.eng.gtefsd.com!howland.reston.ans.net!pipex!demon!wildcard.demon.co.uk!cyber_surfer
Subject: Re: Could this be a BAD thing?
References: <37kuhe$p4l@hobbes.cc.uga.edu> <korcuska-1810941305290001@korcuska.ils.nwu.edu> <1994Oct18.134139.1524@news.cs.indiana.edu> <CxzH1J.2Hu@wri.com>
Organization: The Wildcard Killer Butterfly Breeding Ground
Reply-To: cyber_surfer@wildcard.demon.co.uk
X-Newsreader: Demon Internet Simple News v1.27
Lines: 17
Date: Sun, 23 Oct 1994 10:41:28 +0000
Message-ID: <782908888snz@wildcard.demon.co.uk>
Sender: usenet@demon.co.uk

In article <CxzH1J.2Hu@wri.com> jbrewer@wri.com "John Brewer" writes:

> Agreed.  I'd say a majority of the defects I find in C are from using "="
> instead of "==", rather than vice versa.  I'm much more likely to omit a
> character than add another.

If I found this was a problem, then I'd probably just define
a macro or two. Something like:

#define set       =
#define equ       ==

I like that much more than "if (-1 == code)", which I see in a lot
of the C books I've read.
-- 
"Internet? What's that?" -- Simon "CompuServe" Bates
http://cyber.sfgate.com/examiner/people/surfer.html
