Proto for Boost mailing list page: Re: [proto] [phoenix][msm] proto limits increased to 10, phoenix broken on trunk (was: [phoenix] not playing nice with other libs)

Subject: Re: [proto] [phoenix][msm] proto limits increased to 10, phoenix broken on trunk (was: [phoenix] not playing nice with other libs)
From: Thomas Heller (thom.heller_at_[hidden])
Date: 2011-05-08 10:54:23

On Sunday, May 08, 2011 02:48:19 PM Thomas Heller wrote:
> On Sunday, May 08, 2011 02:05:43 PM Eric Niebler wrote:
> > On 5/2/2011 6:18 PM, Thomas Heller wrote:
> > > On Mon, May 2, 2011 at 12:54 PM, Eric Niebler <eric.niebler_at_[hidden]> 
> wrote:
> > >> Phoenix is changing the following fundamental constants:
> > >>
> > >>  BOOST_PROTO_MAX_ARITY
> > >>  BOOST_MPL_LIMIT_METAFUNCTION_ARITY
> > >>  BOOST_PROTO_MAX_LOGICAL_ARITY
> > >>  BOOST_RESULT_OF_NUM_ARGS
> > >>
> > >> IMO, Phoenix shouldn't be touching these. It should work as best it can
> > >> with the default values. Users who are so inclined can change them.
> > > 
> > > Eric,
> > > This problem is well known. As of now I have no clue how to fix it 
properly.
> > <snip>
> > 
> > The Proto pre-preprocessing work on trunk has progressed to the point
> > where compiling with all the arities at 10 now compiles *faster* than
> > unpreprocessed Proto with the arities at 5. So I've bumped everything to 10.

Phoenix is up and running now again and should play nice with other libs!

Eric, thanks for pointing it all out and actively working on a fix for this!