on Mon Sep 29 2008, Eric Niebler <eric-AT-boost-consulting.com> wrote:
IMO, a full (re-)review of v3 would largely cover the same ground as the current v2 review. Perhaps as a compromise, we could wind up the v2 review with a basic yea or nea. If we agree we want phoenix, we can put phoenix v3 up for a mini-review before it is merged to trunk. The review would focus on:
- Whether the feedback from the v2 review was accommodated - The new extensibility mechanism - The breaking interface changes from v2 - The migration path from lambda to phoenix - Interoperability with boost::bind and std::bind - Interoperability with other Proto-based DSELs - Compile times
I see phoenix v3 as a hugely important step toward Boost's DSEL unification, so I'm generally in favor of getting more eyes on it before it's shipped.
At first glance, not a bad compromise. -- Dave Abrahams BoostPro Computing http://www.boostpro.com