From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Mattias Engdegård" <mattias.engdegard@gmail.com>, emacs-devel@gnu.org
Subject: Re: master c290b034e0f 1/2: Move `wholenump` alias definition
Date: Sun, 03 Sep 2023 10:46:40 +0000 [thread overview]
Message-ID: <874jkb3567.fsf@posteo.net> (raw)
In-Reply-To: <83v8cr7d3y.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Sep 2023 13:41:37 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Mattias Engdegård <mattias.engdegard@gmail.com>
>> Date: Sun, 3 Sep 2023 12:22:07 +0200
>> Cc: philipk@posteo.net,
>> emacs-devel@gnu.org
>>
>> 3 sep. 2023 kl. 12.07 skrev Eli Zaretskii <eliz@gnu.org>:
>>
>> > I'm guessing that was for compatibility with some other Lisp.
>>
>>
>> Maybe an obscure dialect (can't find it in Common Lisp, MacLisp or Interlisp).
>>
>> The symbol `wholenump` is most commonly seen by users in errors as
>> it's generated by CHECK_FIXNAT. It would be good to change that to
>> the less obscure `natnump`, and it seems implausible that such a
>> change would break any code. Any objections?
>
> You assume that "natnump" will be much more clear? why?
The term natural number is less likely to confuse a reader (though it is
not perfect either, due to disagreements on whether or not 0 is a
natural number).
> It will definitely break decade-long habits, and for what? for the
> benefit of some abstract rigor?
next prev parent reply other threads:[~2023-09-03 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169373450576.30740.4674573984693456027@vcs2.savannah.gnu.org>
[not found] ` <20230903094826.33FFAC045B5@vcs2.savannah.gnu.org>
2023-09-03 9:54 ` master c290b034e0f 1/2: Move `wholenump` alias definition Philip Kaludercic
2023-09-03 10:02 ` Mattias Engdegård
2023-09-03 10:07 ` Eli Zaretskii
2023-09-03 10:22 ` Mattias Engdegård
2023-09-03 10:41 ` Eli Zaretskii
2023-09-03 10:46 ` Philip Kaludercic [this message]
2023-09-03 10:50 ` Eli Zaretskii
2023-09-03 12:07 ` Stefan Kangas
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=874jkb3567.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattias.engdegard@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.
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).