Path: utzoo!attcan!uunet!clyde.concordia.ca!mcgill-vision!snorkelwacker!apple!usc!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!haven!decuac!shlump.nac.dec.com!tkou02.enet.dec.com!diamond
From: diamond@tkou02.enet.dec.com (diamond@tkovoa)
Newsgroups: comp.std.c
Subject: Re: "Broken" compilers
Message-ID: <1640@tkou02.enet.dec.com>
Date: 2 May 90 03:18:33 GMT
References: <1990Apr25.165602.974@craycos.com> <1990Apr26.125851.20728@contact.uucp> <1626@tkou02.enet.dec.com> <16582@haddock.ima.isc.com>
Reply-To: diamond@tkou02.enet.dec.com (diamond@tkovoa)
Organization: Digital Equipment Corporation Japan , Tokyo
Lines: 18

In article <16582@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes:
 >In article <1626@tkou02.enet.dec.com> diamond@tkou02.enet.dec.com (diamond@tkovoa) writes:
 >>In article <1990Apr26.125851.20728@contact.uucp> ross@contact.UUCP (Ross Ridge) writes:
 >>>The macro a expands to 5 517 094 707 031 349 characters.
 >>
 >>Yeah, I thought that was greater than 509.
 >
 >The 509-character limit to which you seem to refer is for a "logical source
 >line", which is what you have after backslash-newline splicing but *before*
 >macro expansion.  Peter's example does not exceed this limit.

A logical source line means *both* before and after macro expansion.  The
limit applies until phase 7.  (I also have a letter from Tom Plum, though
not a formal ANSI ruling, that the limit applies after macro expansion.)

-- 
Norman Diamond, Nihon DEC     diamond@tkou02.enet.dec.com
This_blank_intentionally_left_underlined________________________________________