Date: Wed, 16 Jun 1999 21:42:32 +0200
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id: <199906161942.VAA01399@acp3bf.physik.rwth-aachen.de>
To: cp1v45 AT americasm01 DOT nt DOT com (Campbell, Rolf [SKY:1U32:EXCH])
Cc: djgpp AT delorie DOT com
Subject: Re: #define and lines
Newsgroups: comp.os.msdos.djgpp
Organization: RWTH Aachen, III. physikalisches Institut B
X-Newsreader: TIN [version 1.2 PL2]
Reply-To: djgpp AT delorie DOT com

In article <3767F65C DOT B3E58FDC AT americasm01 DOT nt DOT com> you wrote:
> Is there any way to write a #define who's expansion covers more than one
> line?  I already know how to make the definition span-lines, but when
> expanded, they are cramped on a single line.

No way. OTOH, why would anyone care? C preprocessor output is not
meant to be read by anything but the C compiler, so why bother about
long lines instead of several short ones? 

The only parts of the C programming language where a newline is
required are preprocessing commands, anyway. With the preprocessor
itself being a one-pass operation, you cannot generate preprocessor
commands by macro-expansion, either, so there's no need for the
preprocessor to be able to generate newlines.

--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.