[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Line/column numbers in user supplied exception handlers

From: Dale P. Smith
Subject: Re: Line/column numbers in user supplied exception handlers
Date: Thu, 05 Jul 2001 16:57:18 -0400

Neil Jerram wrote:
> >>>>> "Marius" == Marius Vollmer <address@hidden> writes:
>     Marius> "Dale P. Smith" <address@hidden> writes:
>     >> I also found this in the archives:
>     >>
>     >>
>     >> It sounds like a great idea.  Has anyone thought about it?
>     Marius> Yes, I like it, too.  That is, I like the general idea of
>     Marius> separating the notion of error handlers and non-local
>     Marius> exits.  Or put differently, I think the error handler
>     Marius> should be invoked in the dynamic context of the error.  If
>     Marius> it so desires, the error handler can exit non-locally (or
>     Marius> pass control on to the next error handler, but it can't
>     Marius> return normally).
> I'd like to experiment with this; what I have in mind is, before
> `scm_ithrow (key, arg_list, 1);' in scm_error:
>     scm_c_run_hook (scm_error_hook, scm_cons (key, arg_list));
> Then, just as you say, one of the hook procedures can exit non-locally
> if it wants to; but if none of them do, the scm_ithrow will happen.

I was going to suggest this also.

What if the hook is empty?  Should there be a default procedure that
runs, or should the startup code add the default to the hook?


Dale P. Smith
Treasurer, Cleveland Linux Users Group
Senior Systems Consultant, Altus Technologies Corporation
440-746-9000 x309

reply via email to

[Prev in Thread] Current Thread [Next in Thread]