From: Jonathan Wakely <jwakely@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
gcc-patches@gcc.gnu.org,
Ed Smith-Rowland <3dw4rd@verizon.net>
Subject: Re: [wwwdocs] Document __has_attribute in /gcc-5/changes.html
Date: Tue, 07 Apr 2015 09:10:00 -0000 [thread overview]
Message-ID: <20150407090952.GZ9755@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1504071033320.9357@tuna.site>
On 07/04/15 10:38 +0200, Gerald Pfeifer wrote:
>One question: where it refers to __has_attribute returning a
>date in some cases, would it make sense to provide an example
>or show the format?
The referenced SD-6 document shows the values and format:
http://isocpp.org/std/standing-documents/sd-6-sg10-feature-test-recommendations
I would expect that most people using the macros are going to be
referring to that document anyway.
next prev parent reply other threads:[~2015-04-07 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 18:09 Jonathan Wakely
2015-03-11 18:16 ` Jakub Jelinek
2015-03-11 18:42 ` Jonathan Wakely
2015-04-07 8:38 ` Gerald Pfeifer
2015-04-07 8:41 ` Jakub Jelinek
2015-04-07 9:10 ` Jonathan Wakely [this message]
2015-04-09 23:28 ` Gerald Pfeifer
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=20150407090952.GZ9755@redhat.com \
--to=jwakely@redhat.com \
--cc=3dw4rd@verizon.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@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).