Re: Strange change in bytecmop.el

[Stefan Monnier]

> I think the handling in byteopt.el is about generating bytecode (or
> not doing it, for XEmacs-specific code) while the one in bytecomp.el
> is about not issuing warnings for XEmacs features. For example, it
> silences a warning in flymake.el about the use of
> `multiple-value-bind'.

The one in byteopt.el was introduced mostly to remove spurious warnings.
The fact that it optimizes the bytecode was just a nicve side-effect.
So I'm wondering in which circumstance the new code is useful/necessary.


        Stefan