public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> 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: Wed, 11 Dec 2002 06:46:00 -0000 [thread overview] Message-ID: <20021211144604.12302.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8821; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: andre@kiwisound.de Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Subject: Re: Re: c++/8821: gcc 3.2 problem with overloaded inherited operator Date: Wed, 11 Dec 2002 08:43:28 -0600 (CST) > 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!). Note the distinction I made between overloaded functions and overloaded virtual functions. For some historical reason, a virtual function with a different argument list hides a function with the same name in the base class. This is not the case for non-virtual functions. I just don't know how operators behave. That's the question here. I concede that the behavior is confusing. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-12-11 14:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-11 6:46 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-10 23:16 andre
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=20021211144604.12302.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).