public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/33101] [DR 577] allow typedefs for void in empty parameter list
Date: Sat, 14 Jun 2014 23:06:00 -0000	[thread overview]
Message-ID: <bug-33101-4-CsFXSi8p62@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-33101-4@http.gcc.gnu.org/bugzilla/>

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #19 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Oops, I think the DR577 proper bit isn't done yet ;)


  parent reply	other threads:[~2014-06-14 23:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-33101-4@http.gcc.gnu.org/bugzilla/>
2012-03-16 19:32 ` [Bug c++/33101] Bad C++ error on invalid code: <anonymous> has incomplete type Keith.S.Thompson at gmail dot com
2012-03-16 19:40 ` Keith.S.Thompson at gmail dot com
2012-03-16 20:39 ` [Bug c++/33101] [DR 577] " redi at gcc dot gnu.org
2012-03-16 20:46 ` [Bug c++/33101] [DR 577] allow typedefs for void in empty parameter list redi at gcc dot gnu.org
2012-03-16 21:47 ` Keith.S.Thompson at gmail dot com
2012-03-16 22:54 ` redi at gcc dot gnu.org
2014-06-12 14:09 ` paolo.carlini at oracle dot com
2014-06-14 22:56 ` paolo at gcc dot gnu.org
2014-06-14 23:00 ` paolo.carlini at oracle dot com
2014-06-14 23:06 ` paolo.carlini at oracle dot com [this message]
2014-06-23 17:06 ` paolo at gcc dot gnu.org
2014-06-23 17:08 ` paolo.carlini at oracle dot com

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-33101-4-CsFXSi8p62@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).