public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: andre@kiwisound.de To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: Re: c++/8821: gcc 3.2 problem with overloaded inherited operator Date: Tue, 10 Dec 2002 23:16:00 -0000 [thread overview] Message-ID: <20021211071602.17199.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8821; it has been noted by GNATS. From: andre@kiwisound.de To: bangerth@dealii.org, andre@kiwisound.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: Re: c++/8821: gcc 3.2 problem with overloaded inherited operator Date: Wed, 11 Dec 2002 08:09:02 +0100 bangerth@dealii.org schrieb am 10.12.2002, 23:28:06: > Synopsis: gcc 3.2 problem with overloaded inherited operator > > State-Changed-From-To: open->analyzed > State-Changed-By: bangerth > State-Changed-When: Tue Dec 10 14:28:05 2002 > State-Changed-Why: > I can confirm that this problem exists. However, I am > not sure whether it is really a bug: the operator > you want to call is simply hidden by the operator > in the derived class. What I don't know is how lookup > of member operators happen -- if the same rule applies > as for virtual functions, then the operator in the base > class is rightfully hidden; if not, then this is a bug. > > On the other hand, if virtual function semantics apply, > then a function similar to -Woverloaded-virtual should > exist. > In my opinion it IS a bug because the operator of the parent class has another argument. So the name resolution should detect the matching operator in the parent class as usual in C++. I think overloaded operators should behave like overloaded functions (where the same thing works!). If its not in the C++ standard I have to believe now in Java or .net ;-)
next reply other threads:[~2002-12-11 7:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-10 23:16 andre [this message] 2002-12-11 6:46 Wolfgang Bangerth
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021211071602.17199.qmail@sources.redhat.com \ --to=andre@kiwisound.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).