Re: [boost] [range/iterators/algorithms/phoenix/bind...] Coordinated Approach

From: Jaakko Järvi (jarvi_at_[hidden])
Date: 2008-07-01 23:31:09

David Abrahams <dave_at_[hidden]> writes:

> Joel de Guzman wrote:
>> Dean Michael Berris wrote:
>>> On Mon, Jun 30, 2008 at 9:37 PM, David Abrahams <dave_at_[hidden]>
>>> wrote:
>> 
>>>>>> lambda/phoenix/bind
>>>> * Incompatible placeholders
>>>> * Been waiting for the lambda/phoenix merger forever
>>>> * Lambda has lots of limitations and gotchas that we can improve on now
>>>> * Phoenix 2.0 not in Boost
>>>>
>>>
>>> Is Phoenix 2.0 not in the review queue yet?
>> 
>> CC'ing both Jaakko and Eric.
>
> Jaakko is at TAMU now; I can send you his address if you want.
>
>> One of the obstacles towards merger is that Lambda has some
>> quirks of its own that makes it difficult to provide full backwards
>> compatibility. Eric ported Phoenix 2.0 to proto, making it Phoenix
>> 3.0. In the course of the development, Eric and I seem to both
>> coming to the conclusion that the best route is to leave the
>> Lambda codebase alone and make Phoenix 3.0 the new lambda
>> (i.e. lambda 2.0). And, similar to what we did with Spirit2,
>> we can have an interim release that bundles both the old lambda
>> and the new. With this approach, code that uses Lambda should
>> should not do anything special. Users who want to take advantage
>> of the features of Lambda-2 (aka Phoenix) can upgrade with some
>> minimal code tweaks. If this is an acceptable solution to all
>> parties involved (Jaakko?)
>
> If it works for Jaakko, it works for me.

My first reply didn't make it to the list.
Yes, this would be a good arrangement.

  Jaakko