From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: PLEASE: debugging embedded guile code
Date: 26 Apr 2003 16:34:50 +0100 [thread overview]
Message-ID: <m34r4l8e79.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <Pine.GSO.4.33.0304261706460.1619-100000@sunanh>
>>>>> "Joris" == Joris van der Hoeven <TeXmacs@math.u-psud.fr> 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?
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.
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?
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2003-04-26 15:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.33.0304261706460.1619-100000@sunanh>
2003-04-26 15:34 ` Neil Jerram [this message]
2003-04-26 15:40 ` PLEASE: debugging embedded guile code Joris van der Hoeven
2003-04-26 19:30 ` Neil Jerram
2003-04-27 8:40 ` Joris van der Hoeven
[not found] <Pine.GSO.3.96.1030209200016.26546A-100000@anh>
2003-02-25 14:19 ` Joris van der Hoeven
2003-02-25 14:36 ` Dale P. Smith
2003-04-26 14:51 ` Neil Jerram
2003-04-26 16:40 ` Bruce Korb
2003-04-26 19:12 ` Neil Jerram
2003-04-26 20:13 ` Bruce Korb
2003-04-27 20:49 ` Neil Jerram
2003-04-27 21:57 ` Bruce Korb
2003-04-28 15:54 ` Paul Jarc
2003-04-28 16:07 ` Bruce Korb
2003-04-28 19:21 ` Neil Jerram
2003-04-28 20:06 ` Bruce Korb
2003-04-28 20:58 ` Neil Jerram
2003-05-16 17:19 ` Bruce Korb
2003-05-16 19:23 ` Neil Jerram
2003-05-16 20:27 ` Bruce Korb
2003-05-16 21:21 ` Rob Browning
2003-05-16 21:56 ` Bruce Korb
2003-05-17 0:31 ` Bruce Korb
2003-05-17 2:33 ` Bruce Korb
2003-05-19 15:00 ` Paul Jarc
2003-04-28 13:52 ` Mikael Djurfeldt
2003-04-28 19:26 ` Neil Jerram
2003-04-26 14:45 ` 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=m34r4l8e79.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@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).