Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ginosko!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: This one bit me today
Message-ID: <1071@crdos1.crd.ge.COM>
Date: 13 Oct 89 17:38:50 GMT
References: <832@crdos1.crd.ge.COM> <9999@cbnews.ATT.COM>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: GE Corp R&D Center
Lines: 21

In article <9999@cbnews.ATT.COM>, smk@cbnews.ATT.COM (Stephen M. Kennedy) writes:

|  Why did you put this in the pointers section?  This is just a poorly
|  parenthesized macro.  Consider "y = 1 / xavag(10);" or "xavg(n * 10)".

  Oops! I meant pointers as in "helpful hints", not the "pointer to
TYPE" sense. This is a section on common errors, and a few not so
common but really hard to find. 

  When trying to tell students to use loads of parens in macros defs I
liked the example as a case of something which appears to work but
fails because the parens are missing. Based on feedback from students,
a "horrible example" of what can happen if done wrong helps make the
warning stick.

  My use of 'Pointers" was certainly not clear in context.
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon