From: Geert Bosch <bosch@gnat.com>
To: Brad Lucier <lucier@math.purdue.edu>
Cc: jsm28@cam.ac.uk, gcc@gcc.gnu.org
Subject: Re: Manual style: "non-zero" vs "nonzero"
Date: Tue, 09 Oct 2001 12:49:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10110091547100.5314-100000@nile.gnat.com> (raw)
In-Reply-To: <200110091940.f99JeIw28319@banach.math.purdue.edu>
As a final drop, the GNU Coding Standards uses nonzero unhyphenated:
| There should be a comment on each static variable as well, like this:
|
| /* Nonzero means truncate lines in the display;
| zero means continue them. */
| int truncate_lines;
-Geert
next prev parent reply other threads:[~2001-10-09 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 16:20 Brad Lucier
2001-10-08 20:50 ` Russ Allbery
2001-10-09 10:27 ` Phil Edwards
2001-10-09 10:43 ` Joseph S. Myers
2001-10-09 12:40 ` Brad Lucier
2001-10-09 12:49 ` Geert Bosch [this message]
2001-10-09 13:27 ` Gerald Pfeifer
2001-10-10 2:59 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2001-10-08 15:33 Joseph S. 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=Pine.GSO.4.10.10110091547100.5314-100000@nile.gnat.com \
--to=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
--cc=lucier@math.purdue.edu \
/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).