From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Backtrace and enhanced catch
Date: Sat, 04 Feb 2006 15:41:55 +0000 [thread overview]
Message-ID: <8764nv167w.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87slr06jdk.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 04 Feb 2006 11:46:31 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> The spec for catch's pre-unwind-handler would be that it can exit
>> either normally or non-locally. If it exits normally, Guile unwinds
>> (dynamic context + stack) and then calls the normal (post-unwind)
>> handler. If it exits non-locally, that exit determines the
>> continuation.
>
> Hmm. Now my head hurts.
:-) Sorry about that!
Well anyway, I feel pretty confident about it all, and the code's now
in CVS.
> I'm not so sure what I want any more (apart from a reliable
> backtrace).
That's working now.
>> But if we want to be ultra-cautious we could keep lazy-catch as it
>> is and introduce `with-pre-unwind-handler' (or something) with the
>> proposed semantics.
>
> Better be pretty strictly compatible, it's hairy enough without
> changing between guile versions.
Yes, that's what I thought too, so I took the "ultra-cautious"
approach.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-04 15:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 0:16 gh_inexact_p error in 1.7.x Bruce Korb
2005-12-01 0:44 ` Kevin Ryde
2005-12-05 4:08 ` No way out Bruce Korb
2005-12-05 4:35 ` Bruce Korb
2005-12-07 1:31 ` Marius Vollmer
2005-12-05 22:20 ` Kevin Ryde
2005-12-06 10:58 ` Han-Wen Nienhuys
2005-12-28 15:59 ` Neil Jerram
2005-12-31 15:09 ` Han-Wen Nienhuys
2005-12-31 15:14 ` Neil Jerram
2006-01-01 19:58 ` Han-Wen Nienhuys
2006-01-02 15:42 ` Neil Jerram
2006-01-02 18:54 ` Neil Jerram
2006-01-04 21:13 ` Backtrace and enhanced catch Neil Jerram
2006-01-14 12:41 ` Neil Jerram
2006-01-22 13:47 ` Marius Vollmer
2006-01-23 20:11 ` Neil Jerram
2006-01-24 21:34 ` Marius Vollmer
2006-01-16 8:38 ` Ludovic Courtès
2006-01-18 23:08 ` Neil Jerram
2006-01-19 9:38 ` Ludovic Courtès
2006-01-21 11:26 ` Neil Jerram
2006-01-26 23:29 ` Kevin Ryde
2006-01-27 19:30 ` Neil Jerram
2006-01-31 20:07 ` Kevin Ryde
2006-02-01 23:04 ` Neil Jerram
2006-02-04 0:46 ` Kevin Ryde
2006-02-04 15:41 ` Neil Jerram [this message]
2005-12-07 1:07 ` No way out Marius Vollmer
2005-12-07 1:55 ` Rob Browning
2005-12-13 20:32 ` Marius Vollmer
2005-12-28 16:09 ` 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=8764nv167w.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).