From: Joseph Myers <joseph@codesourcery.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Aldy Hernandez <aldyh@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: value_range_base::{non_zero_p, set_zero, set_non_zero}
Date: Fri, 31 May 2019 01:44:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1905310107280.25485@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5b4d0a49-693d-457d-b635-f6445706bd9f@gmail.com>
On Thu, 30 May 2019, Martin Sebor wrote:
> This, of course, is in contrast to things like bit-field and
> built-in where the convention calls for the hyphen but where
For both bit-field and nonzero what we do in documentation is consistent
with the C standard, even if code is less consistent. (grep on the C
standard sources shows 148 lines matching for nonzero and only 2 for
non-zero.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-05-31 1:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 7:49 Aldy Hernandez
2019-05-31 0:08 ` Jeff Law
2019-05-31 0:59 ` Martin Sebor
2019-05-31 1:44 ` Joseph Myers [this message]
2019-05-31 9:05 ` Aldy Hernandez
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.21.1905310107280.25485@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.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).