This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/15910] can't compile self defined void distance(std::vector<T>, std::vector<T>)
- From: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Aug 2005 11:58:01 -0000
- Subject: [Bug libstdc++/15910] can't compile self defined void distance(std::vector<T>, std::vector<T>)
- References: <20040610143911.15910.king.benjamin@mh-hannover.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gdr at integrable-solutions dot net 2005-08-06 11:57 -------
Subject: Re: can't compile self defined void distance(std::vector<T>, std::vector<T>)
"adah at netstd dot com" <gcc-bugzilla@gcc.gnu.org> writes:
| (In reply to comment #44)
| > | However, I still believe it is the problem of the compilers.
| > Please take ti to the C++ standard committee. The behaviour is that
| > described by the standard. If you don't like it, have the committee
|
| The behaviour I wanted is at least not *against* the standard, while being more
| natural and user-friendly. As James Kanze quoted §14.7.1/5 in
| comp.lang.c++.moderated: "If the overload resolution process can determine the
| correct function to call without instantiating a class template definition, it
| is unspecified whether that instantiation actually takes place."
Can you explain me clearly how that has any implication about how the
compiler should behave in this specific case? We're not in an
unspecified territory here. Please do read Paul M.'s explanation.
This PR should be colsed as INVALID.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15910