From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Neil Jerram Newsgroups: gmane.lisp.guile.devel,gmane.lisp.guile.user Subject: Re: PLEASE: debugging embedded guile code Date: 28 Apr 2003 20:26:42 +0100 Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Message-ID: References: <20030225093608.6a8935f8.dsmith@altustech.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1051562132 2822 80.91.224.249 (28 Apr 2003 20:35:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 28 Apr 2003 20:35:32 +0000 (UTC) Cc: Joris van der Hoeven Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Mon Apr 28 22:35:25 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19AFLR-0000j6-00 for ; Mon, 28 Apr 2003 22:35:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19AFKC-0001AP-08 for guile-devel@m.gmane.org; Mon, 28 Apr 2003 16:34:08 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 19AFIf-0000p3-00 for guile-devel@gnu.org; Mon, 28 Apr 2003 16:32:33 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 19AFIO-0000Y1-00 for guile-devel@gnu.org; Mon, 28 Apr 2003 16:32:20 -0400 Original-Received: from mail.uklinux.net ([80.84.72.21] helo=s1.uklinux.net) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19AFI6-0000DR-00; Mon, 28 Apr 2003 16:31:58 -0400 Original-Received: from laruns.ossau.uklinux.net (bts-0105.dialup.zetnet.co.uk [194.247.48.105]) by s1.uklinux.net (8.11.6p2/8.11.6) with ESMTP id h3SKVrK17970; Mon, 28 Apr 2003 21:31:53 +0100 Original-Received: from laruns.ossau.uklinux.net.ossau.uklinux.net (localhost [127.0.0.1])ESMTP id 931D4DC4D4; Mon, 28 Apr 2003 20:26:42 +0100 (BST) Original-To: djurfeldt@nada.kth.se In-Reply-To: Original-Lines: 36 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 Original-cc: guile-devel@gnu.org Original-cc: "Dale P. Smith" Original-cc: guile-user@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Developers list for Guile, the GNU extensibility library List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.devel:2231 gmane.lisp.guile.user:1864 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:1864 >>>>> "Mikael" == Mikael Djurfeldt writes: Mikael> Neil Jerram 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 _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel