On 5/5/2011 12:32 AM, Eric Niebler wrote:
I'll also need to investigate why Proto depends on
BOOST_MPL_LIMIT_METAFUNCTION_ARITY.
Proto no longer depends on BOOST_MPL_LIMIT_METAFUNCTION_ARITY. At least,
not on trunk.
I'm working on pre-preprocessing stuff. So far, it doesn't seem to be
having
I agree. I don't think there really is a general solution to that.
There have been reports
by Micheal Caisse of some macro definition nightmare while using MSM
together with spirit.
If i remember the details correctly, MSM changes the proto constants as well.
This problem is not really
On Thu, May 5, 2011 at 5:47 AM, Eric Niebler e...@boostpro.com wrote:
We're talking about picking a sane and useful default for
BOOST_PROTO_MAX_ARITY. You seem to be saying that 10 would cover most
practical uses of your EDSL. Is that right?
Yep, 10 would be a much better default, the limit of
On Wed, May 4, 2011 at 7:55 PM, Eric Niebler e...@boostpro.com wrote:
Bart, how high can N go in your EDSL? Is it really arbitrarily large?
I didn't hit any limit in the real application (most complicated case
is at 9) and just did a test that worked up to 30. Compilation (debug
mode) took about
On Thu, May 5, 2011 at 5:47 AM, Eric Niebler e...@boostpro.com wrote:
On 5/5/2011 2:27 AM, Bart Janssens wrote:
On Wed, May 4, 2011 at 7:55 PM, Eric Niebler
eric-xT6NqnoQrPdWk0Htik3J/w...@public.gmane.org wrote:
Bart, how high can N go in your EDSL? Is it really arbitrarily large?
I didn't
