Subject: Re: [boost] [phoenix] not playing nice with other libs
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2011-05-02 17:31:52
On 02/05/2011 13:18, Thomas Heller wrote:
> Let me sketch why i changed these constants:
> 1) Phoenix V2 has a composite limit of 10:
> This is equivalent to the number of child expressions a expression can hold.
> This is controlled by BOOST_PROTO_MAX_ARITY for the number of
> template arguments for proto::expr and proto::basic_expr
> 2) Boost.Bind can take up to 10 parameters in the call to boost::bind
> The default BOOST_PROTO_MAX_ARITY is 5.
> The BOOST_RESULT_OF_NUM_ARGS constant needed to be changed because i
> needed to provide 11 arguments in a "call" to boost::result_of. But i
> guess a workaround
> can be found in this specific case.
What is in in Phoenix that intrinsically requires this?
Is it just for the unit tests? Then manually set the right values just
for the unit tests.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk