From: Eric Blake <eblake@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
jemmy858585@gmail.com, "Lidong Chen" <lidongchen@tencent.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, mreitz@redhat.com,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-img: fix some spelling errors
Date: Mon, 24 Apr 2017 10:47:55 -0500 [thread overview]
Message-ID: <f9ce81bc-72d5-d436-5cb6-58c9dbb10aa4@redhat.com> (raw)
In-Reply-To: <7bb35794-6a50-c92f-fee7-e8f9cc55a1d0@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
On 04/24/2017 10:37 AM, Philippe Mathieu-Daudé wrote:
>>> /*
>>> - * Returns true iff the first sector pointed to by 'buf' contains at
>>> least
>>> - * a non-NUL byte.
>>> + * Returns true if the first sector pointed to by 'buf' contains at
>>> least
>>> + * a non-NULL byte.
>>
>> NACK to both changes. 'iff' is an English word that is shorthand for
>> "if and only if". "NUL" means the one-byte character, while "NULL"
>> means the 8-byte (or 4-byte, on 32-bit platform) pointer value.
>
> I agree with Lidong shorthands are not obvious from non-native speaker.
>
> What about this?
>
> * Returns true if (and only if) the first sector pointed to by 'buf'
> contains
That might be okay.
> * at least a non-null character.
But that still doesn't make sense. The character name is NUL, and
non-NULL refers to something that is a pointer, not a character.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-04-24 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 14:33 [Qemu-devel] [PATCH 1/2] qemu-img: make sure contain the consecutive number of zero bytes jemmy858585
2017-04-23 14:33 ` [Qemu-devel] [PATCH 2/2] qemu-img: fix some spelling errors jemmy858585
2017-04-24 14:40 ` Eric Blake
2017-04-24 15:37 ` Philippe Mathieu-Daudé
2017-04-24 15:47 ` Eric Blake [this message]
2017-04-24 15:53 ` Eric Blake
2017-04-25 2:10 ` 858585 jemmy
2017-04-25 19:11 ` Max Reitz
2017-04-26 8:05 ` 858585 jemmy
2017-04-24 14:43 ` [Qemu-devel] [PATCH 1/2] qemu-img: make sure contain the consecutive number of zero bytes Eric Blake
2017-04-25 1:50 ` 858585 jemmy
2017-04-25 19:20 ` Eric Blake
2017-04-25 20:01 ` Max Reitz
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=f9ce81bc-72d5-d436-5cb6-58c9dbb10aa4@redhat.com \
--to=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=jemmy858585@gmail.com \
--cc=kwolf@redhat.com \
--cc=lidongchen@tencent.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).