From: Joseph Myers <joseph@codesourcery.com>
To: Zack Weinberg <zackw@panix.com>
Cc: Rical Jasan <ricaljasan@pacific.net>, <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: manual: Refactor documentation of CHAR_BIT.
Date: Mon, 19 Jun 2017 15:01:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706191501020.27712@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4682bc34-5db8-faae-d0e2-1d89e17619d3@panix.com>
On Sat, 17 Jun 2017, Zack Weinberg wrote:
> On 06/17/2017 04:42 AM, Rical Jasan wrote:
> > This single-@item @table is better defined with @defvr, since the
> > CHAR_BIT macro has @standards (being declared in a header), and @items
> > in @tables are not considered annotatable. Using @defvr automatically
> > includes the macro in the Variable and Constant Macro Index and
> > ensures its inclusion the Summary of Library Facilities.
>
> This part of the change is OK.
>
> > The file include/limits.h identifies the macro as coming from C99.
>
> I think this macro really was in C90, and
> http://flash-gordon.me.uk/ansi.c.txt includes it, which is the closest I
> can come to checking. Joseph, do you know for sure?
CHAR_BIT is C90.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-19 15:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 8:42 manual: Update @standards for [__]va_copy Rical Jasan
2017-06-17 8:42 ` manual: Refactor documentation of CHAR_BIT Rical Jasan
2017-06-17 13:53 ` Zack Weinberg
2017-06-19 15:01 ` Joseph Myers [this message]
2017-06-20 11:23 ` [PATCH v2] " Rical Jasan
2017-06-20 13:44 ` [PATCH v3] " Rical Jasan
2017-06-22 13:23 ` Florian Weimer
2017-07-27 11:31 ` Rical Jasan
2017-07-27 12:22 ` Florian Weimer
2017-07-27 13:13 ` Rical Jasan
2017-06-20 12:11 ` Florian Weimer
2017-06-20 12:16 ` Zack Weinberg
2017-06-17 13:59 ` manual: Update @standards for [__]va_copy Zack Weinberg
2017-06-17 18:32 ` Andreas Schwab
2017-06-20 11:03 ` [PATCH v2] " Rical Jasan
2017-07-27 10:25 ` [PING] " Rical Jasan
2017-08-10 12:11 ` Rical Jasan
2017-08-10 16:34 ` Florian Weimer
2017-08-11 3:01 ` 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.1706191501020.27712@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 \
--cc=zackw@panix.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).