Newsgroups: comp.lang.dylan
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!yeshua.marcam.com!uunet!sytex!smcl
From: smcl@sytex.com (Scott McLoughlin)
Subject: Re: Could this be a BAD thing?
Message-ID: <NXcDuc1w165w@sytex.com>
Sender: bbs@sytex.com
Organization: Sytex Access Ltd.
References: <JRD.94Oct17153331@netcom3.netcom.com>
Date: Tue, 18 Oct 1994 02:04:10 GMT
Lines: 23

jrd@netcom3.netcom.com (Jon Degenhardt) writes:

> In article <37t046$ic4@darkstar.UCSC.EDU> panzer@cse.ucsc.edu (John Panzer) w
> 
> >  The common mistake is that the Dylan initialization syntax will IMHO
> >  lead to the same sort of hard-to-see bugs which are exemplified by
> >  "if (i=42)" in C.
> 
> I know people who write  "if (42==I)"  just to avoid this sort of problem.
> (i.e. Accidentally writing  "if (42=I)"  will fail to compile.)
> 
> --Jon

Howdy,
        Yup - that's what I do when I can't write
(if (eq i 42)...) ;-)  I'm used to writing C this way
now. OTOH, I get lazy and miss more cases of two var
comparisons, e.g. if(a = /*whoops*/ b)...

=============================================
Scott McLoughlin
Conscious Computing
=============================================
