From: Joseph Myers <joseph@codesourcery.com>
To: Rical Jasan <ricaljasan@pacific.net>
Cc: <libc-alpha@sourceware.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH 3/3] manual: Add new header and standards annotations.
Date: Fri, 25 Nov 2016 16:17:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611251607520.8172@digraph.polyomino.org.uk> (raw)
In-Reply-To: <bd36c88b-678f-fa5d-a03f-e15448130385@pacific.net>
On Fri, 25 Nov 2016, Rical Jasan wrote:
> On 11/23/2016 09:42 AM, Joseph Myers wrote:
> > In stdio.h,
> > SEEK_SET, SEEK_CUR, SEEK_END are all likewise C90.
>
> What about the other 2 headers? I had:
>
> @comment stdio.h unistd.h fcntl.h
> @comment ISOC99, POSIX, XOPEN || XOPEN2K8
>
> Do you want:
>
> @comment stdio.h unistd.h fcntl.h
> @comment C90, POSIX, XOPEN || POSIX.1-2008
Well, I'd like that comment in summary.awk saying what the intended syntax
actually is in the case of multiple headers (how the standards are to be
matched to the headers). But:
For stdio.h it's C90.
For unistd.h it's POSIX.1 (i.e. 1990 edition, in the list I gave of
possible notation for standards).
For fcntl.h it's XOPEN || POSIX.1-2008.
So if comma-separated standards correspond to space-separated headers,
it's as you say except for my proposed notation saying POSIX.1 for the
1990 edition.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-25 16:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 6:38 [PATCH 0/3] manual: Header & Standards Cleanup Rical Jasan
2016-11-23 6:38 ` [PATCH 3/3] manual: Add new header and standards annotations Rical Jasan
2016-11-23 17:42 ` Joseph Myers
2016-11-24 10:22 ` Rical Jasan
2016-11-24 13:37 ` Joseph Myers
2016-11-25 5:59 ` Rical Jasan
2016-11-25 14:53 ` Joseph Myers
2016-11-25 15:09 ` Joseph Myers
2016-11-30 10:39 ` Rical Jasan
2016-11-30 10:45 ` Florian Weimer
2016-11-30 12:50 ` Joseph Myers
2016-12-02 11:54 ` Rical Jasan
2016-12-02 13:56 ` Joseph Myers
2016-12-05 7:59 ` Rical Jasan
2016-11-30 12:38 ` Joseph Myers
2016-12-05 5:33 ` Rical Jasan
2016-12-05 18:22 ` Joseph Myers
2016-12-06 10:57 ` Rical Jasan
2016-12-06 15:59 ` Joseph Myers
2016-12-06 16:36 ` Zack Weinberg
2016-11-25 7:36 ` Rical Jasan
2016-11-25 16:17 ` Joseph Myers [this message]
2016-11-30 10:46 ` Rical Jasan
2016-11-30 12:52 ` Joseph Myers
2016-11-23 6:38 ` [PATCH 2/3] manual: Convert @tables of variables to @vtables Rical Jasan
2016-11-23 6:38 ` [PATCH 1/3] manual: Refactor header and standards annotations Rical Jasan
2016-11-23 17:31 ` Joseph Myers
2016-11-24 9:34 ` Rical Jasan
2016-11-24 13:17 ` Joseph Myers
2016-11-25 3:44 ` Rical Jasan
2016-11-25 14:25 ` Joseph Myers
2016-11-30 8:58 ` Rical Jasan
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.1611251607520.8172@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mtk.manpages@gmail.com \
--cc=ricaljasan@pacific.net \
/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).