Re: PLEASE: debugging embedded guile code

[Neil Jerram]

>>>>> "Mikael" == Mikael Djurfeldt <address@hidden> writes:

    Mikael> Neil Jerram <address@hidden> writes:
    Dale> The answer is lazy-catch. [...]

    Mikael> In fact, it's better to use

    Mikael>   scm_internal_stack_catch

    Mikael> in which case some of the complexity disappears.

True; I've used stack-catch in my latest suggestion.

    >> 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.)

    Mikael> One obvious reason is that there is no documentation.  We
    Mikael> should really have a simple example of how to enable
    Mikael> debugging from C and how to use scm_internal_stack_catch
    Mikael> to print out all error information.

I agree w.r.t. documentation but am not convinced about C.  I'm
beginning to think that Guile should actively encourage people to do
as much as possible in Scheme, and I see no reasons (yet) why this
kind of error handling has to be done in C.

    Mikael> Regarding looking for new/better solutions: It's probably
    Mikael> good to follow closely what happens with regard to error
    Mikael> handling in the SRFI process.  Relevant SRFIs are, at
    Mikael> least, 34, 18 (exception handlers, `raise' in thread
    Mikael> context), 23, 35, 36.

Thanks - I'll take a look.

        Neil