"Eric Niebler" <eric@boost-consulting.com> writes:
David Abrahams wrote:
pongba <pongba@gmail.com> writes:
Eric Niebler <eric <at> boost-consulting.com> writes:
Incrementing the 'BOOST_MPL_..._LIMIT_ARITY'(I forgot the detail though) doesn't help though, because the arity of mpl::apply will increase correspondingly and will always be one more arity than that mpl::lambda can support! It's inherent conflict or inconsistence.
Did I miss any obvious alternative?;-)
Eric can use the appropriate applyN template.
Ah, thanks. Using applyN instead of apply fixes the problem. The fact that apply doesn't work here seems like a bug to me. Is it fixable?
Not really, without changing how it is used. It's the arity problem that pongba pointed out. You'd have to write something like: apply<some_lambda_expression>::to<a, b, c> -- Dave Abrahams Boost Consulting www.boost-consulting.com