|
Boost Users : |
From: Joel de Guzman (joel_at_[hidden])
Date: 2008-07-21 03:19:39
Joel de Guzman wrote:
> John C. Femiani wrote:
>> Joel de Guzman wrote:
>>> John C. Femiani wrote:
>> <snip>
>>>> I think it is also confusing that fusion sequences are mpl sequences
>>>> IF you include 'fusion/mpl.hpp', but not if you include
>>>> 'fusion/adapted/mpl.hpp'. I would like to see that in the docs
>>>> please (it took me some time to figure out).
>>>
>>> Will do. Just out of curiosity, how did you figure it out? Which
>>> section in the docs did you look into first? Thanks!
>> I'll answer in reverse order.
>>>
>>> Which section in the docs did you look into first?
>> First, I wanted the types in a fusion sequence as an mpl sequence. I
>> googled, and found the introduction of the Fusion library, (which I
>> had read before) :
>>
> [snip long story]
>>
>> to the header for FusedConcept, everything worked.
>
> Ok, sorry for the troubles. I'll improve the docs to make this info
> easier to find. It is indeed lacking. Thanks for your support.
Ok, done. I added this to the adapted docs:
[heading Header]
#include <boost/fusion/adapted.hpp>
#include <boost/fusion/include/adapted.hpp>
Fusion sequences may also be adapted as fully conforming __mpl__ sequences (see
__intrinsics__). That way, we can have 2-way adaptation to and from __mpl__ and
Fusion. To make Fusion sequences fully conforming __mpl__ sequences, include:
#include <boost/fusion/mpl.hpp>
If you want bi-directional adaptation to and from __mpl__ and Fusion, simply
include:
#include <boost/fusion/include/mpl.hpp>
The header includes all the necessary headers.
Regards,
-- Joel de Guzman http://www.boostpro.com http://spirit.sf.net
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net