Subject: Re: [boost] [mpl][docs]why use list?
From: Larry Evans (cppljevans_at_[hidden])
Date: 2009-03-23 08:30:44
On 03/23/09 06:11, Dmitry Goncharov wrote:
> Larry Evans wrote:
>> Unfortunately, following the directions on:
>> Does anyone know what I might be doing wrong?
> You can find the answer here
Thank you, Dmitry.
AFAICT, this is a documentation bug. Although limit-vector-size.html
[Note: Overriding will take effect only if the library is configured
not to use preprocessed headers. See
BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS for more information. end note]
When defined, it instructs the MPL to discard the pre-generated
headers found in boost/mpl/aux_/preprocessed directory and use
preprocessor metaprogramming techniques to generate the necessary
versions of the library components on the fly.
suggests that mpl will do the metaprogramming when, in fact,
the user must either do the metaprogramming:
or the user must first invoke a python program to generate
some headers before doing the compile:
If nobody disagrees (within the next day or so), I'll
create a trac-ticket for this doc bug.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk