Re: Change in bytecomp.el breaks Gnus

[Stefan Monnier]

>     Many of those warnings are bogus.
> Perhaps the ones that remain are bogus, but that's because I fixed
> many real ones that used to occur.

Indeed.  I find the warning very useful.

>     One of the most common case of "bogus" is when a CL function is used
>     in a macro and this macro is only used inside the file, so it's only
>     used during byte-compilation and never at runtime.

> I think the right fix for that is with-no-warnings.  However, it could be
> that the code that generates this warning can be improved.

Yes, I have no good idea how to improve it, but hopefully an idea will show
up at some point.  In the mean time with-no-warning is the best we have.


        Stefan