dan marsden wrote:

Joel de Guzman wrote:

...

Mathias Gaunard wrote:

...

Joel de Guzman wrote: Isn't the move to first-class Boost citizen a good opportunity to change some parts of the interface, and thus give a new version number? Indeed. As noted in the review blurb, V3 will be the future of phoenix. The V3 interface will be assumed. The most major interface shifts are:

1) ET engine: Use of Boost.Proto 2) Result type deduction: Use of Boost.Typeof 3) Type deduction protocol: Use of Boost.Resultof

As far as the interface goes, we can take all that for granted. We have the proof of concept.

I think I'd add to your list of major interface shifts: 4) Extension protocol: The current extension approach is tightly coupled to the hand rolled expression templates, and will need changing for a proto based v3, unless if I've missed yet more genius from Eric?

I'm not that smart. ;-) I haven't yet thought about v3's extension protocol. Extending Phoenix may require some Proto hacking, but it's possible that Phoenix could provide a high-level extension interface that hooks Proto behind the scenes. Not sure yet. -- Eric Niebler BoostPro Computing http://www.boostpro.com