Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Macro names imbedded in pp-numbers [repost]
Message-ID: <11652@smoke.BRL.MIL>
Date: 19 Nov 89 06:59:36 GMT
References: <11134@riks.csl.sony.co.jp> <15217@haddock.ima.isc.com> <1643@crdos1.crd.ge.COM> <11641@smoke.BRL.MIL> <3060@splut.conmicro.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <3060@splut.conmicro.com> jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard) writes:
>Uhm, Doug...does this mean that the behavior of a program differs with
>the use or non-use of white space? Isn't this different from the rest of C?

No, white space has always been significant for preprocessing.  Consider:
	#define	foo	(void)
	foo bar();
	foobar();

White space is also sometimes significant outside preprocessing:
	a = b / *c;	/* comment */	;
	a = b/*c;	/* comment */	;
This was even worse when we had =op assignment operators.

The latter example strikes me as quite analogous to the pp-number situation.