unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: saving and restoring the error stack trace
Date: Fri, 01 Sep 2006 08:34:00 +0100	[thread overview]
Message-ID: <87zmdkavmf.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <15846551.1156820926538.JavaMail.root@web13> (dsmich@adelphia.net's message of "Mon, 28 Aug 2006 23:08:46 -0400")

<dsmich@adelphia.net> writes:

> ---- Neil Jerram <neil@ossau.uklinux.net> wrote: 
>
>> 5.21.2 Debugging when an error occurs
>
>    ...
>
> Thank you, thank you!  This bit of documentation has been sorely
> needed for a long time.

That's true.  Over the last few years it's a question that has been
regularly asked on the mailing lists, and never quite definitively
answered.

>  Many people come to Guile from the "C side"
> with poor or nonexistant Scheme experience.  Usually to add Guile to
> some C application, which of course throws out the REPL and it's
> backtracing and error reporting capabilities.  So then when errors
> happen you have no idea where or how.  Making a C program extended
> by Guile spit out a proper backtrace is a twisty maze of handlers
> and catchers, and some of them need to be lazy.  (Lazy? Why would I
> want a *lazy* handler, I want a hard-working, full-featured kind of
> handler, not some wimpy light weight *lazy* handler!)

:-)

> My point is that getting good backtraces from C is non-obvious and a
> huge hindrance to people just learning how to use Guile and Scheme.
> But that's over now.  Thanks again Neil.

Thanks for your kind words.

Regards,
     Neil



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2006-09-01  7:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29  3:08 saving and restoring the error stack trace dsmich
2006-09-01  7:34 ` Neil Jerram [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-01 20:10 Marco Maggi
2006-08-31  6:04 Marco Maggi
2006-09-01  7:47 ` Neil Jerram
2006-09-01  9:39   ` Ludovic Courtès
2006-09-07 22:11     ` Neil Jerram
2006-08-25  9:39 Marco Maggi
2006-08-27 12:53 ` Neil Jerram
2006-08-28 22:21   ` Neil Jerram
2006-09-07  9:02     ` Volkan YAZICI
2006-09-07 21:36       ` Neil Jerram
2006-09-08  6:09         ` Volkan YAZICI
2006-08-24 19:34 Marco Maggi
2006-08-24 21:53 ` Neil Jerram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zmdkavmf.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).