Re: [boost] [phoenix] request for a mini-review. (Re: Phoenix as a Boost library)

Subject: Re: [boost] [phoenix] request for a mini-review. (Re: Phoenix as a Boost library)
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2010-10-16 09:33:17

> >> On 10/13/2010 8:39 PM, Joel de Guzman wrote:
> >>> On 10/14/2010 11:22 AM, Edward Diener wrote:
> >>>> On 10/13/2010 10:50 PM, Joel de Guzman wrote:
> >>>>> On 10/14/2010 10:41 AM, Edward Diener wrote:
> >>>>>> I am curious to know if Phoenix will ever be released as a Boost
> >>>>>> library, or is it meant to be forever coupled with Spirit?
> >>>>>>
> >>>>>> I have avoided it because it has never been released separately
> >>>>>> or had its documentation appear among the list of Boost
> >>>>>> libraries. I got the impression that it would be released
> >>>>>> separately, and expected to see it in Boost 1.44, but evidently
> >>>>>> that did not happen.
> >>>>>
> >>>>> Thomas Heller completed the Proto port last July. Now the next
> >>>>> step is to have a mini-review. Then, Boost integration, IFF it
> >>>>> passes the mini-review.
> >>>>
> >>>> Thanks ! I am sure I am not the only one looking forward to seeing
> >>>> it as a library of its own, and using it, if it passes the
> >>>> mini-review.
> >>>
> >>> Let us request for a mini-review then. I think it's about time.
> >>> Thomas? Eric?
> >>
> >> The Proto port is done, but in the process of writing docs, Thomas
> >> realized there were some things about the Phoenix intermediate
> >> representation that would make extensibility difficult. He's been
> >> working on it. The design discussion is active on the proto list.
> >> (Chime in, I'd love your feedback.)
> >
> > Indeed, I was missing you in the whole discussion Joel :)
> 
> Oh my, I just looked and you guys are miles ahead. I'm not sure I can keep
> up.
> 
> Anyway, having said that, just keep in mind that people have been
> clamoring for phoenix and I'd prefer something done sooner rather than
> later. We can tweak the library later as long as the main interface (not
> the extension interface) is stable. And it has remained more or less
> stable for a long time now. IMO, it should be a priority to focus on the
> remaining incompatibilities before anything else.
> 
> IMO, phoenix has surpassed the Boost bar even at V2. Interestingly, the
> bar has been set higher for this particular library due to other factors
> such as putting on the shoes of lambda, the inter-operability and proto,
> etc. I think it's about time to finish up and conclude that it is "good
> enough" :-)
> 
> I'm sure, thanks to you, Eric and all the amazing people here, that it'll
> get better over time. But let us get it into boost first.

FWIW, as the review manager of Phoenix2, and the one who suggested this mini
review, I'd be happy to manage that review as well (if nobody objects, that
is).

Regards Hartmut
---------------
http://boost-spirit.com