Daniel Walker wrote:
On Mon, Sep 29, 2008 at 9:33 AM, Giovanni Piero Deretta <gpderetta@gmail.com> wrote:
Note that I think that the extension interface (and its documentation) is the most important part of Phoenix because, IMHO, it is where the "added value" with respect to boost.lambda lies.
The best solution would be that the implementation that goes into boost will be based on proto *and* will retain more or less the same extension interface.
I agree that extensibility via Proto is an important innovation, and
Just to be clear: the phoenix extension mechanism has been in place from day one (since phoenix1). It is a hallmark of the design that has proven to be very powerful. It allowed us to extend the library in a modular manner non-intrusively. All libraries I have written since then has incorporated some form of extension mechanism. The API basically has two parts, one is the general user API, one is the extension API. Regards, -- Joel de Guzman http://www.boostpro.com http://spirit.sf.net