Peter Scott wrote:
>
> An exception is an 'error'. That's already a vague concept.
I'll say it's vague. There are certainly uses for an exception to
trigger non-local success, not an error at all. In fact, there are
whole programming techniques based on such uses. Just because most
of us usually use exceptions to handle errors, that doesn't mean
Perl should not support other uses.
Not that Peter has been suggesting anything of the sort. I'm
just trying to explain why RFC 88 isn't named "Structured *Error*
Handling Mechanism" ;-)
Hmm. Technically, if Exception is the base class for exception
objects, all errors should be signalled by derivatives of some
Exception::Error class, since not all exceptions are errors.
Oh RSI, and then there's the whole problem managing the namespace
for both core derivative classes and module/application derivative
classes. For now, I think the Exception class should have enough
functionality for both generic exceptions, and error exceptions,
and then we can try to avoid the whole issue.
Yours, &c, Tony Olekshy
