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: 11 Aug 2005 06:46:33 -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-11 06:46 -------
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:
| Hi Gaby,
|
| I have read Sutter's Modest Proposal on fixing ADL that you referred to me. If
| you had told me earlier about this instead of bluntly telling me this was not a
| GCC bug,
It still is NOT a GCC bug, no matter how you put it. GCC
correctly implements the standard specifications. Just because you
happen not to like the consequences of the rules under some
circumstances does not make it a GCC bug. Furthermore, I've suggested
from the very outset that you take the issue to the C++ committee --
which if you have done, you would have discovered the many facets of
fixes you are discovering now. That was no "bluntly telling" you. It
is not a GCC bug, it is a fact. You would have learnt more about the
subject when you took it to the apporpriate place, is also a fact.
But, you were obsessed by the very idea that it must be a GCC bug,
rejecting outright suggestions to take the issue to the appropriate
places and only afterward half-admitting that is what you would have
done and are putting blame on other people for your irrational
refusal to give more thoughts to the issue and move and discuss it in
the apporpriate forums.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15910