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!hookup!swrinde!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> <782908888snz@wildcard.demon.co.uk> <mhamburg-241094105131@macb022.mv.us.adobe.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: 21
Date: Thu, 27 Oct 1994 13:02:24 +0000
Message-ID: <783262944snz@wildcard.demon.co.uk>
Sender: usenet@demon.co.uk

In article <mhamburg-241094105131@macb022.mv.us.adobe.com>
           mhamburg@mv.us.adobe.com "Mark Hamburg" writes:

> The problem with that is that programmers can still easily write the wrong
> thing.  Just because we have some pretty macros doesn't help when a new
> programmer comes onto the project and through force of habit uses = or ==
> and occasionally gets it wrong.

This is true. I've just never had that problem. Perhaps that's coz
I've always used C compilers that warn the programmer of possible
unintended assignments, unless you write:

    if ((s = fget(...)) == NULL)

I only noticed the assignment problem when I started compiling code
written with other compilers, which was a few years ago.

Martin Rodgers
-- 
Please vote for moderation in comp.lang.visual
http://cyber.sfgate.com/examiner/people/surfer.html
