public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: topiolli@ee.oulu.fi To: gcc-gnats@gcc.gnu.org Subject: c++/7428: Precedence in selecting overloaded operators Date: Mon, 29 Jul 2002 00:26:00 -0000 [thread overview] Message-ID: <20020729071955.18100.qmail@sources.redhat.com> (raw) >Number: 7428 >Category: c++ >Synopsis: Precedence in selecting overloaded operators >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jul 29 00:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: topiolli@ee.oulu.fi >Release: g++ (GCC) 3.1.1 >Organization: >Environment: SunOS tk3 5.8 Generic_108528-15 sun4u sparc SUNW,Ultra-80 >Description: I have a template class called SmartPtr that does - guess what. Since it has a typecast operator, it can be used where a pointer to the base type is expected. Also, operator == is overloaded to allow comparison of SmartPtr instances: template <class T> SmartPtr { public: operator T* () { return _internalPtr; } operator const T* () const { return _internalPtr; } }; template <class T> bool operator== (const SmartPtr<T>&, const SmartPtr<T>&); The compiler chokes on this. It cannot figure out whether it should use the overloaded operator to compare SmartPtrs, or should it perhaps use the built-in operators for comparing pointers, because the SmartPtr can be casted to a pointer. The problem is easily solved by removing the overloaded operator, but in my mind the overloaded operator should be the preferred choice as it does not need typecasts. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-07-29 7:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-29 0:26 topiolli [this message] 2002-07-29 1:26 Topi Maenpaa 2002-07-29 1:58 paolo
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=20020729071955.18100.qmail@sources.redhat.com \ --to=topiolli@ee.oulu.fi \ --cc=gcc-gnats@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).