Re: [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-errors at runtime (Bug#27340)

[Johan Bockgård]

Stefan Monnier <address@hidden> writes:

>> Which suggests that declaim's effects are a superset of proclaim's
>> effects. But then it also says
> [...]
>> So I guess we could drop the effects at runtime?
>
> I agree that it's not really clear, but when you look at the doc of
> proclaim and compare it to that of declaim it seems clear what is the
> intention: one is meant to be "runtime only" (which is why it evaluates
> its argument and is just a normal function) while the other is designed
> such that it can be used at compile-time and only affects the
> compilation of the current file (although the doc allows the
> implementation to be less careful and let the effect "leak").

This is wrong. declaim has run-time effects, just like defvar etc. The
compile-time side effect is that it ALSO affects the compilation of the
remainder of the current file.

http://www.lispworks.com/documentation/HyperSpec/Body/03_bcaa.htm