Proto for Boost mailing list page: Re: [proto] [phoenix] not playing nice with other libs

Subject: Re: [proto] [phoenix] not playing nice with other libs
From: Thomas Heller (thom.heller_at_[hidden])
Date: 2011-05-05 01:35:03

On Thu, May 5, 2011 at 5:47 AM, Eric Niebler <eric_at_[hidden]> 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_at_[hidden]> 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 2-3 minutes at that point, with some swapping, so I
>> didn't push it any further.
>>
>> I've attached the header defining the grouping grammar, there should
>> be no dependencies on the rest of our code.
>
> 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?

I think having BOOST_PROTO_MAX_ARITY set to 10 is a good default!