public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gianni@mariani.ws To: gcc-gnats@gcc.gnu.org Subject: c++/10542: warning: choosing `T::operator int&()' over `T::operator const int&() const' Date: Tue, 29 Apr 2003 16:26:00 -0000 [thread overview] Message-ID: <20030429162447.7840.qmail@sources.redhat.com> (raw) >Number: 10542 >Category: c++ >Synopsis: warning: choosing `T::operator int&()' over `T::operator const int&() const' >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Apr 29 16:26:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: gianni@mariani.ws >Release: GCC 3.2.2 >Organization: >Environment: Linux RH 8.0 configure --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit Thread model: posix gcc version 3.2.2 >Description: The warnings below ahould not be issued. The code below should work without problems. g++ tt5.cpp -o tt5 tt5.cpp: In function `int main()': tt5.cpp:53: warning: choosing `IType::operator int&()' over `IType::operator const int&() const' tt5.cpp:53: warning: for conversion from `IType' to `int' tt5.cpp:53: warning: because conversion sequence for the argument is better #include <cassert> class IType { public: int m_value; inline IType() : m_value( 3322-21 ) { } inline operator int & () { return m_value; } inline operator const int & () const { return m_value; } inline int & operator = ( const int & i_value ) { m_value = i_value; return m_value; } }; class tester { public: IType m_int; }; int main() { tester z; const tester * a = & z; assert( z.m_int == 3301 ); assert( a->m_int == 3301 ); return 0; } >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-04-29 16:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-29 16:26 gianni [this message] 2003-04-30 1:13 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=20030429162447.7840.qmail@sources.redhat.com \ --to=gianni@mariani.ws \ --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).