From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp,gnu.gcc.help
Subject:	Re: Preprocessing with gcc
Date:	22 Aug 2001 14:28:48 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	20
Message-ID:	<9m0fj0$ajt$1@nets3.rz.RWTH-Aachen.DE>
References:	<3B83C185 DOT C107E36 AT bigfoot DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 998490528 10877 137.226.32.75 (22 Aug 2001 14:28:48 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	22 Aug 2001 14:28:48 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In comp.os.msdos.djgpp Alex Vinokur <alexvn AT bigfoot DOT com> wrote:
> I would like to preprocess some file using gcc.

Wrong tool for the task. GCC (or it's preproccessor) is *not* a
general-purpose macro preprocessor for textfiles, and the problem
you're facing is one typical symptom of that.

> However the reason (abc's) is within
>  #if (0) ... #endif

> Why does gcc detect that ?

Because even text inside #if 0 ...  #endif is still required to be
formally correct C Preprocessor input, by the C language definiton.
Your text isn't.

You had better use m4 for this.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -