From: Joseph Myers <joseph@codesourcery.com>
To: Jason Merrill <jason@redhat.com>
Cc: Marek Polacek <polacek@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: C/C++ PATCH to add __remove_qualifiers (PR c/65455, c/39985)
Date: Wed, 13 Sep 2017 16:37:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1709131634510.29579@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CADzB+2mQ1xKgrxuVkEUtrYoq5aSiqP7z1-jkTk7BBE7yCmxrPg@mail.gmail.com>
On Sat, 9 Sep 2017, Jason Merrill wrote:
> > +@code{__remove_qualifiers} takes a typename as an argument:
>
> I think it would be better to use the term "type-id" here, to avoid
> confusion with "type-name", which is only a single identifier.
There's no such thing as a type-id in C, and type-name is the term used in
C syntax (for what goes in a cast, etc.).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-09-13 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 16:59 Marek Polacek
2017-08-31 17:23 ` Joseph Myers
2017-09-01 12:46 ` Marek Polacek
2017-09-09 13:55 ` Jason Merrill
2017-09-13 16:37 ` Joseph Myers [this message]
2017-09-13 16:55 ` Joseph Myers
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=alpine.DEB.2.20.1709131634510.29579@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=polacek@redhat.com \
/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).