From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Chunyang Xu <mail@xuchunyang.me>, 24875@debbugs.gnu.org
Subject: bug#24875: 26.0.50; In Dotted Pair Notation, the read function returns CDR if CAR is absent
Date: Tue, 06 Jul 2021 12:43:58 -0400 [thread overview]
Message-ID: <jwvbl7ftn4q.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zguzpiet.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 06 Jul 2021 17:32:26 +0200")
Lars Ingebrigtsen [2021-07-06 17:32:26] wrote:
> Chunyang Xu <mail@xuchunyang.me> writes:
>
>> For example, I eval this in the *scratch* buffer:
>>
>> (read "( . 123)")
>> ⇒ 123
>>
>> (read "(1 . ( . (3 . nil)))")
>> ⇒ (1 3)
>>
>> I can't find explanation about this behavior in elisp manual. Is it
>> expected?
>
> That is indeed very eccentric behaviour, so we should probably mention
> it somewhere? (I guess we can't change it.)
>
> Anybody got an opinion here, or a way that we can describe it in the
> manual except pointing at the examples and then going ¯\_(ツ)_/¯?
It's the "natural" behavior if you start from
(Ea . Ed)
as the notation for cons cells and extend it to
(E1 E2 E3 .. . Ed)
such that
(E1 {foo} . Ed) = (E1 . ({foo} . Ed))
because then you replace `{foo}` with the empty sequence and you get:
(E1 . Ed) = (E1 . ( . Ed))
and hence
Ed = ( . Ed)
It's not used very often, so in theory we could potentially change it,
but I haven't seen any good alternative interpretation for it, and
I don't see the benefit of signaling an error.
Stefan
next prev parent reply other threads:[~2021-07-06 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 13:36 bug#24875: 26.0.50; In Dotted Pair Notation, the read function returns CDR if CAR is absent Chunyang Xu
2016-11-04 16:00 ` Andreas Schwab
2016-11-04 16:00 ` Drew Adams
2021-07-06 15:32 ` Lars Ingebrigtsen
2021-07-06 16:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-07-06 17:15 ` Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2021-05-18 15:04 Drew Adams
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=jwvbl7ftn4q.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=24875@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mail@xuchunyang.me \
--cc=monnier@iro.umontreal.ca \
/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).