public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61753] poor diagnostic for constructor definition that starts with 'const'
Date: Tue, 08 Jul 2014 17:59:00 -0000	[thread overview]
Message-ID: <bug-61753-4-vFC80nWXGN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61753-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61753

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[4.7.2 regression]          |poor diagnostic for
                   |prototype for function does |constructor definition that
                   |not match any in class      |starts with 'const'
                   |error                       |

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I don't know how you got that to compile with GCC 4.6.3 as every version I have
rejects it - not a regression.

(The upstream code on github has been fixed now btw)


  parent reply	other threads:[~2014-07-08 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 17:24 [Bug c++/61753] New: [4.7.2 regression] prototype for function does not match any in class error shapero at uw dot edu
2014-07-08 17:46 ` [Bug c++/61753] " redi at gcc dot gnu.org
2014-07-08 17:59 ` redi at gcc dot gnu.org [this message]
2014-07-09  0:36 ` [Bug c++/61753] poor diagnostic for constructor definition that starts with 'const' shapero at uw dot edu
2015-08-31 15:44 ` paolo.carlini at oracle dot com
2015-09-01  8:40 ` paolo at gcc dot gnu.org

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=bug-61753-4-vFC80nWXGN@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).