Juho Snellman writes:
> Richard M Kreuter <kreuter@...> writes:
> > Hi,
> > Does anybody have strong objections to extending the scope of
> > SB-EXT:MUFFLE-CONDITIONS to include conditions raised outside of
> > compilation proper?
> Presumably you mean only a very limited set of conditions
> (eg. redefinition warnings), not having it apply to everything?
Configurably handling redefinition warnings is the proximate goal, yes.
However, it seemed to me that if there's one context in which the user
might want to have a customizable muffling of conditions, then maybe
he'd want it all the time (i.e., rather than allowing muffling of
conditions only in the compiler or only in the compiler and in LOAD,
allowing it to be done globally).
> This has been discussed a bit before.
I don't see much consensus in that thread, except perhaps that everybody
agrees that annoying warnings are annoying. ISTM that rather than
negotiating just when to signal the warning, it's simpler to always
signal a warning containing enough information to support
separately-maintained definitions of uninterestingness, and to give the
user a global knob for using his preferred definition of uninteresting
decide what to muffle.