Subject: Re: [boost] [GSoC][Phoenix3] Regarding mutability of arguments passed to phoenix expressions
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2010-06-12 17:34:28
Le 12/06/2010 20:39, David Abrahams a écrit :
Quoted out of order:
> As it is, IMO it's still going to be better than the built-in lambdas.
The only real problem I have with built-in lambdas myself is the lack of
The fact they're quite verbose (unlike the very terse lambda or phoenix
v2) is something I dislike, but that I can live with.
For captures, I don't see how anyone would want to do anything but
capture everything by reference.
> I know. I'm beginning to think that if we could only (appropriately)
> change the rules for overriding -> and add (an appropriate) operator.,
> Phoenix would be the indisputable hands-down winner.
Unfortunately, the only decent way of overloading operator. I can think
of is to take a polymorphic function object that takes obj, arg1, ...,
argN and calls obj.name_to_overload(arg1, ..., argN).
Problem is, that's only usable if you've got polymorphic lambda expressions.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk