Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of
 stephan.bergmann.secondary@googlemail.com designates 209.85.161.47 as
 permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: [code] stuck at offapi on unxlngx6.pro
From: Stephan Bergmann <stephan.bergmann.secondary@googlemail.com>
In-Reply-To: <1314645963.10931.YahooMailClassic@web113505.mail.gq1.yahoo.com>
Date: Tue, 30 Aug 2011 08:47:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7686367-4254-49CB-8975-BC1163B66A42@googlemail.com>
References: <1314645963.10931.YahooMailClassic@web113505.mail.gq1.yahoo.com>
To: ooo-dev@incubator.apache.org,
 giffunip@tutopia.com

On Aug 29, 2011, at 9:26 PM, Pedro F. Giffuni wrote:
>> any reason why we build our own preprocessors and don't use
>> the C toolchain preprocessor that is already required to
>> build OOo?
>>=20
>=20
> This is an important question. If we need another
> preprocessor there are options(1), but we need to now
> why.

At least for idlc, I think the best solution would be to get rid of a C =
preprocessor completely.  Even if de-facto (if not also de-jure) .idl =
files have always been passed through a C preprocessor, so in theory =
could make use of all the C preprocessor's features, this has =
practically always only been used for plain #include <=85> or #include =
"=85" stuff (plus internal and external header guards, #ifndef =
XXX/#define XXX/.../#endif and #ifndef XXX/#include "YYY"/#endif), I =
think.

So, it should be possible---without breaking backwards compatibility in =
practice---to change idlc so that it ignores all #=85 lines except for =
#include lines, which it then handles via a more efficient mechanism =
than textual inclusion.

Would still have to have a look at soltools/cpp, though...

-Stephan=