Luke Palmer wrote:
So, maybe what's needed is a C catcher (C... eew),
where C would throw an exception object with an attached
continuation. And of course, if a warning reached the top of the
stack without being caught, it would print itself and invoke its
continuation.
I thought I'd try and see
Luke Palmer <[EMAIL PROTECTED]> writes:
> This is more of a language thang, so I've redirected your message
> there [here].
>
>> The most fundamental feature throwing an exception is that it transfers
>> program execution from the call site. Allowing the caller to resume
>> execution at that site
This is more of a language thang, so I've redirected your message
there [here].
> The most fundamental feature throwing an exception is that it transfers
> program execution from the call site. Allowing the caller to resume
> execution at that site is a very dangerous form of action at a distance.
