Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!ken
From: ken@cs.rochester.edu (Ken Yap)
Newsgroups: comp.lang.c
Subject: Re: #define OR ||
Message-ID: <1990Feb1.085531.3099@cs.rochester.edu>
Date: 1 Feb 90 08:55:31 GMT
References: <5940014@hpcupt1.HP.COM> <Jan.24.10.40.15.1990.15842@police.rutgers.edu> <33889@ucbvax.BERKELEY.EDU> <1922@gmdzi.UUCP> <33948@ucbvax.BERKELEY.EDU> <1941@gmdzi.UUCP>
Reply-To: ken@cs.rochester.edu
Organization: University of Rochester Computer Science Department
Lines: 15
Address: Rochester, NY 14627, (716) 275-1448

|This is the old slogan: UNIX users always *know* what they do; C users always
|*know* what they do. To my experience, practice and the discussions in
|comp.lang.c prove the contrary. So why not help them to avoid some common
|pitfalls by defining some adequate macros?

But macros introduce their own pitfalls too. I once wanted to strangle
the programmer who wrote

#define	K	*1000

so that one could write:

	resistance = 10K;

You can imagine what happened when somebody declared the variable K.