Re: Automatially move from $n (was: C++11 move semantics)

[Frank Heckenbach]

Akim Demaille wrote:

> > As I wrote, if Bison could detect multiple uses and warn, that would
> > be great, but I didn't look into it as I didn't want to patch Bison
> > itself.
> 
> Agreed.  But then, the syntax you choose, is a little weird:
> the syntax is quite generic (we apply some treatment to $k,
> which could be for instance printing its value (stupid, but
> why not)), but the warning would be really specific for move.

Indeed, I had considered both things separately, but together they
don't make too much sense.

> Shouldn't we go for something like %define api.value.move,
> or api.rhs.move, or api.rhs.rvalue, etc.  I mean, as a Boolean
> value, not a generic placeholder.

Might be better then (and would work for me, of course). Unless
someone comes up with another valid use of the more generic feature
(then we'd have to see how the warning would interact with it).

Regards,
Frank