bug#1132: =5397cquote=5397d does not signal error when given 2 or more args

bug#1132: =5397cquote=5397d does not signal error when given 2 or more args

[xah lee]

Summary: perhaps the “quote” special form should signal an error  
when given more than one argument?


Detail:

I was trying to write a mode , working on my font-lock-keywords...

after few hours of frustration and help from gnu.emacs.help, it turns  
out that the “quote” takes one argument only.

i.e.

'(...)
is equivalent to
(quote (...))
not
(quote ...)

However, elisp does not indicate any error when “quote” is given  
more than one argument. Perhaps this is something that can be improved?

Kevin Rodgers wrote:
«Indeed.  Is it a bug that quote does not signal "Wrong number of  
arguments"?  I know that special forms do not necessarily evaluate  
their arguments, but neither do macros and eval/apply manages to make  
sure that the number of supplied arguments conforms to a macro's  
argument list.»

... For what's worth.

   Xah
∑ http://xahlee.org/

☄

bug#1132: =5397cquote=5397d does not signal error when given 2 or more args

[Andreas Schwab]

xah lee <xah@xahlee.org> writes:

> Summary: perhaps the “quote” special form should signal an error when
> given more than one argument?

This is already fixed in Emacs 23.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

bug#1132: quote does not signal error when given 2 or more args

[martin rudalics]

 > Summary: perhaps the “quote” special form should signal an error when
 > given more than one argument?

It does:

   if (!NILP (Fcdr (args)))
     xsignal2 (Qwrong_number_of_arguments, Qquote, Flength (args));

Try (quote foo bar) ...

 > I was trying to write a mode , working on my font-lock-keywords...

Errors occuring during fontification must not disrupt redisplay so you
won't see them most of the time.  That's what probably happened in your
case.

martin