This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/16347] Some cases of calling constructor with temporary object still not recognised properly
- From: "matthew_bugzilla at datadeliverance dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jul 2004 06:03:38 -0000
- Subject: [Bug c++/16347] Some cases of calling constructor with temporary object still not recognised properly
- References: <20040703124146.16347.matthew_bugzilla@datadeliverance.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From matthew_bugzilla at datadeliverance dot com 2004-07-05 06:03 -------
(In reply to comment #1)
> B b(A(i)); // This doesn't
> means a function which returns the type B and takes A as an agrument,
> So this is not a bug, there has been a couple of dups like this before.
I can see that B b(A) means that, but surely B b(A(i)) can't be a function
declaration - what does the (i) mean in that case? And why does it correctly
interpret B b(A(1)) as instantiating a B?
Thanks
-Matthew
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16347