public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Keith.S.Thompson at gmail 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: Fri, 16 Mar 2012 21:47:00 -0000	[thread overview]
Message-ID: <bug-33101-4-x6jRlzZrSx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-33101-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Keith Thompson <Keith.S.Thompson at gmail dot com> 2012-03-16 21:41:18 UTC ---
On re-reading DR 577, I agree that it implies the current standard
says that only "(void)" is allowed, and in particular that a typedef
is not.  I might have interpreted it differently myself, but I defer to
the committee.  (I thought perhaps that the change had been made between
N3290 and the released standard, but apparently that's not the case.)

The fact that C90 required the keyword further weakens my previous
argument.

So the diagnostic is necessary, but I'd still suggest that a warning
would be more appropriate, and would still meet the current standard's
requirements.

(I should mention that I have no need for this myself; I don't even take
advantage of the permission to use "(void)" rather than "()".)


  parent reply	other threads:[~2012-03-16 21:42 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 [this message]
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
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-x6jRlzZrSx@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).