Re: master abe5eb9: Explain what ( . c) means to the Emacs Lisp reader

[Philip Kaludercic]

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