Re: Towards a cleaner build

[Stefan Monnier]

>> Note that if a function/variable FOO is defined as obsolete in file BAR, then
>> I think we'd ideally want to silence all warnings for uses of FOO made
>> within BAR.
> Determining the current file is easy enough (with
> `byte-compile-current-file'), but what's the best way to determine what
> file that obsolete function came from?

I'm not suggesting we encode the above condition in the code.
As I said elsewhere, I think trying to be too clever in which warnings
to automatically silence quickly gets to diminishing returns.

More important is the support for the author to be able to silence those
warnings which are false positives since that works regardless if we could
come up with a way to detect it automatically or not.


        Stefan