24 Jan
2011
24 Jan
'11
8:18 p.m.
AMDG On 1/24/2011 10:38 AM, Hossein Haeri wrote:
Well, isn't this addressable in Boost PP?
No. Boost.PP can't change how the compiler searches for headers.
I obviously didn't mean this. See below please.
I mean, can Boost PP just not make its expansion compatible with this cross-compiler issue?
Like I have also said above, I am asking for Boost PP to adapt itself with this cross-platform issue. To put it differently, why is BOOST_PP_FILENAME_1 not portable? Can Boost PP please address that?
Adapt? How? All that Boost.Preprocessor does is #include BOOST_PP_FILENAME_1. There's nothing else it /can/ do. In Christ, Steven Watanabe