From: Drew Adams <drew.adams@oracle.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: RE: master a9f147a: Use the full name of the null byte/character, not its abbreviation
Date: Mon, 5 Oct 2020 12:34:12 -0700 (PDT) [thread overview]
Message-ID: <84d7c924-9716-45ca-a99d-d585a6483ff8@default> (raw)
In-Reply-To: <87wo04sclj.fsf@igel.home>
> >> -@xref{Lisp and Coding Systems, inhibit-nul-byte-detection}.
> >> +@xref{Lisp and Coding Systems, inhibit-null-byte-detection}.
> >
> > I think this patch is ill-advised.
> >
> > AFAIK "NULL" is a pointer of zero value, whereas the byte/char of zero
> > value is called "NUL",
>
> NUL is the ASCII abbreviation (TLA) of the null character.
Yes. The character is called the null character or
the null byte character, or sometimes a null byte.
https://en.wikipedia.org/wiki/Null_character
See bug #43780, which unfortunately was closed as "not a bug".
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43780
IMO, this variable renaming was gratuitous and ill-advised.
Can we please revert this renaming from "null" to "nul"?
Or if you insist that we allow the new name, with "nul",
can we at least unobsolete the former (and better) name,
with "null"?
prev parent reply other threads:[~2020-10-05 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201005182136.10826.67802@vcs0.savannah.gnu.org>
[not found] ` <20201005182138.AE01D209B9@vcs0.savannah.gnu.org>
2020-10-05 19:05 ` master a9f147a: Use the full name of the null byte/character, not its abbreviation Stefan Monnier
2020-10-05 19:21 ` Andreas Schwab
2020-10-05 19:34 ` Drew Adams [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84d7c924-9716-45ca-a99d-d585a6483ff8@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).