Re: [Boost-users] [lambda] helping lambda to deduce return type and then avoid 'ret<T>'

Subject: Re: [Boost-users] [lambda] helping lambda to deduce return type and then avoid 'ret<T>'
From: Joel de Guzman (joel_at_[hidden])
Date: 2010-05-28 23:43:55

On 5/29/10 8:50 AM, alfC wrote:
>
>
> On May 24, 5:05 pm, OvermindDL1<overmind..._at_[hidden]>  wrote:
>> On Mon, May 24, 2010 at 2:51 PM, Matthias Schabel
>>> You should take a look at<boost/units/lambda.hpp>  - Torsten Maehne contributed it to deal with interplay betweenlambdaandunits... Something similar might be worthwhile with interval as well.
>>
>> or Boost.Phoenix, it handles such things better.
>
> OvermindDL1, you are right,
> while lambda with units needs to explicitly  to #include<boost/units/
> lambda.hpp>
> boost phoenix works out of the box
>
> 	cout<<  (boost::lambda::_1+boost::lambda::_1)(energy)<<endl;  //
> needs #include "boost/units/lambda.hpp"
> 	cout<<  (boost::phoenix::arg_names::arg1 +
> boost::phoenix::arg_names::arg1)(energy)<<endl;

Glad to hear. Anyway, it'll get even better. Right now, we're in the
development stage of Phoenix-3 using proto. As you know, Phoenix-3
will be the next lambda. Boost-lambda will still be available, but
will be in maintenance mode (and for backward compatibility) as soon
as we get Phoenix-3 in the distribution.

Regards,
-- 
Joel de Guzman
http://www.boostpro.com
http://spirit.sf.net