* Re: master abe5eb9: Explain what ( . c) means to the Emacs Lisp reader
[not found] ` <20210706171404.117E720B72@vcs0.savannah.gnu.org>
@ 2021-08-24 14:45 ` Stefan Kangas
2021-08-25 10:25 ` Philip Kaludercic
0 siblings, 1 reply; 3+ messages in thread
From: Stefan Kangas @ 2021-08-24 14:45 UTC (permalink / raw)
To: Emacs developers, Lars Ingebrigtsen
Lars Ingebrigtsen <larsi@gnus.org> writes:
> diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi
> index d8091f1..365d5ac 100644
> --- a/doc/lispref/objects.texi
> +++ b/doc/lispref/objects.texi
> @@ -1001,6 +1001,13 @@ It looks like this:
> @end example
> @end ifnottex
>
> + As a somewhat peculiar side effect of @code{(a b . c)} and
> +@code{(a . (b . c))} being equivalent, for consistency this means
> +that if you replace @code{b} here with the empty sequence, then it
> +follows that @code{(a . c)} and @code{(a . ( . c))} are equivalent,
> +too. This also means that @code{( . c)} is equivalent to @code{c},
> +but this is seldom used.
This really is nitpicking but... should we perhaps say something even
stronger here, for example "almost never used"?
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: master abe5eb9: Explain what ( . c) means to the Emacs Lisp reader
2021-08-24 14:45 ` master abe5eb9: Explain what ( . c) means to the Emacs Lisp reader Stefan Kangas
@ 2021-08-25 10:25 ` Philip Kaludercic
2021-08-25 10:50 ` Lars Ingebrigtsen
0 siblings, 1 reply; 3+ messages in thread
From: Philip Kaludercic @ 2021-08-25 10:25 UTC (permalink / raw)
To: Stefan Kangas; +Cc: Lars Ingebrigtsen, Emacs developers
Stefan Kangas <stefan@marxist.se> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi
>> index d8091f1..365d5ac 100644
>> --- a/doc/lispref/objects.texi
>> +++ b/doc/lispref/objects.texi
>> @@ -1001,6 +1001,13 @@ It looks like this:
>> @end example
>> @end ifnottex
>>
>> + As a somewhat peculiar side effect of @code{(a b . c)} and
>> +@code{(a . (b . c))} being equivalent, for consistency this means
>> +that if you replace @code{b} here with the empty sequence, then it
>> +follows that @code{(a . c)} and @code{(a . ( . c))} are equivalent,
>> +too. This also means that @code{( . c)} is equivalent to @code{c},
>> +but this is seldom used.
>
> This really is nitpicking but... should we perhaps say something even
> stronger here, for example "almost never used"?
Is it ever used?
--
Philip Kaludercic
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-08-25 10:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20210706171402.18082.17826@vcs0.savannah.gnu.org>
[not found] ` <20210706171404.117E720B72@vcs0.savannah.gnu.org>
2021-08-24 14:45 ` master abe5eb9: Explain what ( . c) means to the Emacs Lisp reader Stefan Kangas
2021-08-25 10:25 ` Philip Kaludercic
2021-08-25 10:50 ` Lars Ingebrigtsen
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.