Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!twwells!bill
From: bill@twwells.com (T. William Wells)
Newsgroups: comp.lang.c
Subject: Re: #define OR ||
Message-ID: <1990Feb3.234642.11292@twwells.com>
Date: 3 Feb 90 23:46:42 GMT
References: <5940014@hpcupt1.HP.COM> <Jan.24.10.40.15.1990.15842@police.rutgers.edu> <1990Jan25.192545.1570@twwells.com> <1933@gmdzi.UUCP>
Organization: None, Ft. Lauderdale, FL
Lines: 28

In article <1933@gmdzi.UUCP>, Georg Wittig writes:
: bill@twwells.com (T. William Wells) writes:
:
: >EQ is relatively harmless, but also pointless. There are better
: >ways to make sure you don't substitute an = for an ==.
:
:         Please do tell me those better ways.

Well, besides using a compiler that checks for them, writing a
tiny program to do the checking for you is one. Such programs
aren't a big deal to write; a simple sed script might be enough.

Now, I don't make enough of this particular error to make such a
program worthwhile for me; but you may. Writing such scripts,
personalized for your own gremlins, is a good way to deal with
them.

:
:                 const == variable       instead of
:                 variable == const
:
:         is *not* better for the following reasons:

Ugh, I agree.

---
Bill                    { uunet | novavax | ankh } !twwells!bill
bill@twwells.com