Re: References to temporaries and function-calls
Sylvester Hesp wrote:
"Victor Bazarov" <v.Abazarov@comAcast.net> wrote in message
news:er213q$c3b$1@news.datemas.de...
Sylvester Hesp wrote:
"Gavin Deane" <deane_gavin@hotmail.com> wrote in message
news:1171547463.242146.302480@s48g2000cws.googlegroups.com...
On 15 Feb, 13:16, "Erik Wikstr?m" <eri...@student.chalmers.se>
wrote:
int main() {
bar(foo());
foo& a_reference = foo();
}
...both statements have the same problem. They both try and bind a
temporary to an non-const reference.
Also keep in mind that for both versions the copy ctor of foo has to
be accessible if the reference were to be const. And this, in fact,
does work
int main()
{
foo& a_reference(foo());
It's a declaration of a function. Of course it "does work".
d'Oh!
I feel so stupid right now.
Nevertheless, why the need for accessible copy ctors?
Because during binding to a reference a copy may need to be made.
It is needed if conversion happens, as in
void foo(const int&);
foo(3.1415926); // the temporary 'int' is created and bound
// to the reference
As to why the need to make a copy... I am not sure. Try looking
in the archives. This undoubtedly has been discussed before. Just
search for "accessible copy constructor bind reference" (without
the quotes).
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask