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: c++/7016 Date: Thu, 23 Jan 2003 15:46:00 -0000 [thread overview] Message-ID: <20030123154600.9643.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7016; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/7016 Date: Thu, 23 Jan 2003 09:41:08 -0600 (CST) [Originally blocked by spam filter, just as following messages] ---------- Forwarded message ---------- Date: Thu, 23 Jan 2003 06:51:42 +0000 From: Neil Booth <neil@daikokuya.co.uk> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jbeulich@novell.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/7016: missing definitions for <?= and >?= bangerth@dealii.org wrote:- > This is probably a corner case whether I should close the > report: this has never worked (used to ICE) > --------------------------------- > class C {}; > C operator <?= (C) { return C(); } > -------------------------------------- > I don't think it was ever documented that one should be > able to overload this operator (a gcc extension anyway). > Now we at least get a reasonable error: > g/a> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc > x.cc:2: error: expected identifier > x.cc:2: error: expected type-name > x.cc:2: error: expected `,' or `;' > > So the fact that the new parser rejects the code is ok, and > is not removing a documented extension. The documentation should say one way or the other. FWIW to me allowing overloading is TRT. Neil.
next reply other threads:[~2003-01-23 15:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-23 15:46 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-23 17:06 c++/7016 Wolfgang Bangerth 2003-01-23 16:46 c++/7016 Wolfgang Bangerth 2003-01-23 15:46 c++/7016 Wolfgang Bangerth 2003-01-23 15:46 c++/7016 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=20030123154600.9643.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).