From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Use of continuations in eval traps
Date: Fri, 28 Oct 2005 22:18:50 +0100 [thread overview]
Message-ID: <87hdb19w79.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <66e540fe0510281354m2eb93928p17aa82de7b1a4d5f@mail.gmail.com> (Mikael Djurfeldt's message of "Fri, 28 Oct 2005 22:54:08 +0200")
Mikael Djurfeldt <mdjurfeldt@gmail.com> writes:
> You are probably more competent to answer the question than me.
:-) Well thanks for your quick response anyway; it's very helpful.
> I wrote that code when I was pretty inexperienced, and the choice to
> allow for the continuation to be saved was probably more motivated by
> a feeling that I didn't want any limitations on what you could do with
> traps than anything more specific---except that I probably had
> imagined the continuations as a way to resume execution after a
> breakpoint, of course.
Oh yes, I remember now; continuations have not been necessary for
continuing after a breakpoint since this change to call the trap
handlers directly instead of executing a throw:
2001-06-26 Neil Jerram <neil@ossau.uklinux.net>
* eval.h, eval.c (scm_call_4): New function.
* eval.c (SCM_APPLY, SCM_CEVAL, ENTER_APPLY): Call trap handlers
directly rather than dispatching to them via scm_ithrow and a lazy
catch.
* eval.c (scm_evaluator_trap_table), eval.h (SCM_ENTER_FRAME_HDLR,
SCM_APPLY_FRAME_HDLR, SCM_EXIT_FRAME_HDLR): Add three new options
for trap handler procedures.
* debug.h (SCM_RESET_DEBUG_MODE): Add checks for trap handler
procedures not being #f.
(I hope I didn't miss anything by making this change ... I think I
checked it with you at the time also.)
> I agree that it seems expensive to create the continuation at every
> trap, and your idea to skip the cheaptraps option and delegate the
> decision whether to create the continuation or not to the lazy handler
> code (I assume) seems good.
Cool, I'll give it a go and see what turns out.
> BTW, your work on the debugger and Emacs interface seems really great---thanks!
Thanks again,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-10-28 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 18:56 Use of continuations in eval traps Neil Jerram
2005-10-28 20:54 ` Mikael Djurfeldt
2005-10-28 21:18 ` Neil Jerram [this message]
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=87hdb19w79.fsf@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).