🚀 go-pugleaf

In article <macdev-42A394.02363922092000@news.mit.edu>, meeroh
<macdev@meeroh.org> wrote:

| Then writing:
| 
| Fun (Foo (2));
| 
| is exactly the same as writing
| 
| const Foo   __temporary (2);
| Fun (__temporary);

Just a minor correction to meeroh's excellent explanation.  The temporary
is not const.

class zurk
{
public:
 zurk(int z) {zonk=z;}
 void const_method() const {}
 int zonk;
};
...
 zurk(2).const_method(); // ok

But nevertheless, meeroh's argument holds.  Ref:

13.3.3.1.4 - Reference binding
...
-3- A standard conversion sequence cannot be formed if it requires binding
a reference to non-const to an rvalue (except when binding an implicit
object parameter; see the special rules for that case in
over.match.funcs). [Note: this means, for example, that a candidate
function cannot be a viable function if it  has a non-const reference
parameter (other than the implicit object parameter)  and the
corresponding argument is a temporary or would require one to be created
to initialize the reference (see dcl.init.ref). ] 

And yes, the comiler has gotten stricter in this regard between 5.3 and 6.

-Howard