On 3/20/2012 7:35 PM, Hite, Christopher wrote:
It may work for MPL I just upgraded boost and fusion now checks the limit and complains:
boost_1_49_0/boost/fusion/container/map/detail/preprocessed/as_map.hpp:21:2: error: #error "FUSION_MAX_MAP_SIZE out of bounds for preprocessed headers"
I spent about an hour trying to hack around that. It looks like I'll either have to change boost or copy paste a good deal of fusion's details into a header.
I realize you're not repsonsible for fusion, but as far as I can tell the other libraries copied your techniques and if we figure this out for MPL we can apply it to them too.
No, Fusion does not use MPL's techniques at all. It does not use any scripts to generate the prepreocessed headers. Instead, Fusion uses Wave. Ditto for Phoenix-3. Going beyond the limts is very simple: simply #define BOOST_FUSION_DONT_USE_PREPROCESSED_FILES. Regards, -- Joel de Guzman http://www.boostpro.com http://boost-spirit.com