Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!agate!saturn!sidney
From: sidney@saturn.ucsc.edu (Sidney Markowitz )
Newsgroups: comp.lang.c
Subject: Re: This one bit me today
Message-ID: <9353@saturn.ucsc.edu>
Date: 8 Oct 89 00:22:43 GMT
References: <2432@hub.UUCP> <832@crdos1.crd.ge.COM> <FISCHER.89Oct7213617@dirac.iesd.auc.dk>
Reply-To: sidney@saturn.ucsc.edu (Sidney Markowitz )
Organization: University of California, Santa Cruz
Lines: 12

We were talking about:
	#define xavg(m) (sum+3)/m
and then using the expression:
	xavg(*x)

Interestingly enough cc on this machine (ISI, running BSD 4.3) with
default settings chokes when the macro expands into the beginning of a
comment in (sum+3)/*x, but not when compiled with the -ansi switch.
Doesn't pAns say that comments are converted to whitespace before
macro expansion, so the /* generated by the macro should never be
parsed as a comment?
-- sidney markowitz <sidney@saturn.ucsc.edu)