On Thu, Mar 17, 2011 at 10:24 AM, Daniel James <dnljms@gmail.com> wrote:
On 17 March 2011 08:52, Thomas Heller <thom.heller@googlemail.com> wrote:
There are still some unresolved issues. Mainly how to deal with the migration of Boost.Bind, Boost.Lambda and Phoenix V2. There hasn't been any discussion regarding that.
I don't think it'd be a good idea to do anything to bind or lambda in this release. Was there a consensus on replacing them? Personally, I'd like to keep the existing Boost.Bind, even if in a different namespace. I appreciate its relative simplicity and portability.
I agree, I will propose a battle plan later today on which we can base a discussion and find a consensus. Quick outline on what i have in mind: phoenix::bind is (almost) completely compatible with boost::bind (as already mentioned, I ported all unit tests of boost.bind to phoenix and they pass). The only thing phoenix::bind doesn't support yet is the explicit specification of the return type. I will add support for those. The options here would be to forward boost/bind.hpp to boost/phoenix/bind.hpp and have a macro that allows to use the old bind, defaulting to use the old bind as a start. The situation with Boost.Lambda is different, the interfaces of the libraries are not really compatible. There needs to be more documentation on the phoenix side to guide a BLL to Phoenix. - Thomas