On May 28, 2009, at 12:38 PM, Derick Eddington wrote:
On Thu, 2009-05-28 at 09:53 +0300, Abdulaziz Ghuloum wrote:
For now, I have added a warning message that's printed whenever a
library is considered stale. (we should have a "warnings policy")
I think the warnings policy should be: raise-continuable &warning
exceptions with at least a &message. &warning is non-&serious and so
the base exception handler will return (as required by R6RS, and
Ikarus
already conforms) after printing the exception to (current-error-port)
(which Ikarus already does) and the program will continue. By
default,
this will be similar to what Ikarus is currently doing.
Having a consistent policy of raising continuable (&warning &message
---) exceptions opens the facilities which might cause a warning to
being used (by you or users or psyntax/Ikarus hackers) in new
unforeseen
ways by things which might want to handle these exceptions and do
something arbitrary about them, such as maybe do something or maybe
not
and then maybe return to continue or maybe not.
I've been using continuable &warning in Xitomatl in a few useful ways.
I think it's a very good facility.
You could even subtype &warning into some &ikarus-warning which the
base
handler prints specially, if you don't like the normal exception
printing being used for these warnings. I like the idea of using the
normal exception printing because it makes these warnings searchable
with regular expressions which match normal Ikarus-shaped exception
print-outs.
Sounds good to me. Thanks.
How about a policy for handling these warnings?
I'm thinking, for example, that ikarus --compile-dependencies should
silently continue "&stale" warnings (or is that undesirable?). Maybe
we'll also need --warnings-fatal, --warnings-to-file <filename>, etc.
Aziz,,,
