RE: setq's with missing final arguments.

[Drew Adams]

> > 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.
> 
> This is bug#20241.

I'd forgotten that I filed that bug. ;-)

I disagree with the only reply to that bug report, however:

 From: Stefan Monnier
 > Beyond this particular occurrence, I think that a wrong-number-of-args
 > error should be raised when `setq' is called with an odd number of
 > arguments.

 At the very least the byte-compiler should warn about it, indeed.

A warning is _no_ substitute for raising an error.  Adding a
warning for byte compilation is worse than doing nothing, IMO.

The doc clearly says that an even number of args are _required_.