Re: PLEASE: debugging embedded guile code

[Joris van der Hoeven]

On 26 Apr 2003, Neil Jerram wrote:
> >>>>> "Joris" == Joris van der Hoeven <address@hidden> writes:
>
>     >> I'm curious about this because the question of error handling keeps
>     >> popping up and I'm wondering whether our current solution is good
>     >> enough.  (With a strong suspicion that it isn't.)
>     >>
>     >> One thing I'm not sure I understand is why you want (or perhaps need)
>     >> to do this lazy-catch in C rather than in Scheme, since it would be
>     >> much easier in Scheme.  Can you explain?
>
>     Joris> I now have something more or less satisfactory for myself.
>
> Using lazy-catch?

Yes.

>     Joris> One of the most important shortcomings of the current
>     Joris> situation is probably poor documentation. In particular, I
>     Joris> think that the manual should contain an example how to deal
>     Joris> with detailed error handling.
>
> I agree, but I also think that the lazy-catch mechanism is more tricky
> than it needs to be, especially in C.  So I'd like to get the
> mechanism right first and then document it.

We now started to use lazy-catch more and more, but we might
still change that. Can you tell us what you have in mind?

>     Joris> I also think that there you might add some scheme routines
>     Joris> to construct comprehensive error messages from error
>     Joris> objects.  This would allow me to print these messages in a
>     Joris> popup window or include them in a status buffer. I
>     Joris> currently print everything to standard output or error...
>
> I think I understand, but can you give an example?

You might for instance provide routines

        (error->message error-obj)
        (error->backtrace error-obj)
        (error->source error-obj)
        (error->file-name error-obj)
        (error->line-number error-obj)
        etc.