This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/49574] Give a warning for insane overloading
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 29 Jun 2011 09:20:37 +0000
- Subject: [Bug c++/49574] Give a warning for insane overloading
- Auto-submitted: auto-generated
- References: <bug-49574-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49574
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-06-29 09:20:33 UTC ---
(In reply to comment #1)
> > all the
> > standalones will fail to compile and build their application.
>
> Huh? Why?
Oops, I meant to put that "Why?" below, not here (I know why it fails to
compile :-) not sure what you mean by standalones though)
> > There is no
> > restriction to use those methods inside the library, thus the insane usage can
> > remain hidden.
>
> Huh?
Why is it hidden? If you call foobar(5) it's ambiguous. Your library has
tests, right? :)
I agree a warning when the functions are declared could be useful for finding
the problem earlier