Re: setq's with missing final arguments.

[Andreas Schwab <schwab@linux-m68k.org>]

David Kastrup <dak@gnu.org> writes:

> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> Alan Mackenzie <acm@muc.de> writes:
>>
>>> Hello, Emacs.
>>>
>>> Consider this file:
>>>
>>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>> (defvar foo t)
>>> (defvar bar t)
>>>
>>> (defun bad-setq ()
>>>   "Doc string"
>>>   (setq foo 5
>>> 	bar))
>>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>>
>>> In the setq, there is a missing argument after "bar".  At the moment,
>>> the byte compiler just generates code to assign nil to bar, without
>>> giving any warning.  IMAO, this is Very Bad.
>>
>> But consistent with how setq works.
>
> How so?

Where did I say "documented"?

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."