Boost logo

Boost :

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-12-17 19:19:18


----- Original Message -----
From: "mfdylan" <dylan_at_[hidden]>

> The problem might be reduced by setting up a two-phase compile,
> whereby you create a file designed to be run through the pre-
> preprocessor (using whatever option your compiler has to do such a
> thing), then include that into your regular source file.
> The file effectively gets preprocessed twice - and you can choose
> which bits you want to leave as macros and which bits you want
> expanded.
> I've never tried this however so it might not be that realistic in
> practice.

Sure, but then you have to live with whatever lousy formatting the
preprocessor gives you after pass 1, and possibly the comments are stripped.
At least for development purposes, I would like to have a fully-expanded
version of every file we use PREPROCESSOR on (at least, in any heavy-duty
way) available in the repository. We could handle it with a "shadow"
directory structure, so that developers who care would put the shadow boost
root ahead of the regular one in their path.

-Dave


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk