public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jonny Grant <jg@jguk.org>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>
Subject: Re: argz_create
Date: Tue, 27 Oct 2020 16:47:58 +0100	[thread overview]
Message-ID: <099d5476-da34-c62c-1626-d36e54f659c0@gmail.com> (raw)
In-Reply-To: <eefb1d45-ab48-e32d-596b-43d748f192da@jguk.org>

Hello Jonny,


> However "nonempty" is not an English, or American English expression
> we would ever use. Even "non-empty" isn't English, we'd say "not
> empty", although in this sentence there is no need to have this at
> all....
> Maybe in another 50 years "nonempty" will be a word,
> but for now it isn't, so the hyphen is needed. Same as "non-NULL"

But "nonempty" has been a word for a long, long time.
As in "nonempty set", a term you'd use in maths any day.

"non-empty" (with a hyphen) occurs dozens of times in the 
POSIX standard, just to take an example close to home.

Now, one may argue the point about the hyphen, but
re "non" vs "non-" see, for example,
https://www.chicagomanualofstyle.org/qanda/data/faq/topics/HyphensEnDashesEmDashes/faq0079.html

Opinions obviously differ, but the tendency in English
is that thyphens are going away in these cases. I think CMoS
has got it right.

Things like "non-NULL" are exceptional, and it's because
"NULL" is a keyword in C.

Now, as to whether that word "nonempty" is even needed
in that sentence, I am not sure. Presumably the point isto
contrast with the "(NULL,0)" tuple mentioned in the
preceding sentence. In that sense, it's possibly a helpful
word, though I'm not sure it's necessary.

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2020-10-27 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 14:18 argz_create Jonny Grant
2020-10-26 16:08 ` argz_create Michael Kerrisk (man-pages)
2020-10-26 16:16   ` argz_create Michael Kerrisk (man-pages)
2020-10-26 21:12     ` argz_create Jonny Grant
2020-10-27 10:43       ` argz_create Jonny Grant
2020-10-27 13:01         ` argz_create Michael Kerrisk (man-pages)
2020-10-27 15:03           ` argz_create Jonny Grant
2020-10-27 15:47             ` Michael Kerrisk (man-pages) [this message]
2020-10-26 21:08   ` argz_create Jonny Grant

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=099d5476-da34-c62c-1626-d36e54f659c0@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=jg@jguk.org \
    --cc=linux-man@vger.kernel.org \
    /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