unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mdj@mit.edu>
Cc: djurfeldt@nada.kth.se, Guile Development <guile-devel@gnu.org>
Subject: Re: lazy-handler-dispatch and debug-on-error
Date: Wed, 26 Nov 2003 12:27:39 -0500	[thread overview]
Message-ID: <xy7y8u359bo.fsf@chunk.mit.edu> (raw)
In-Reply-To: <m3ptfqu294.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "17 Nov 2003 21:13:59 +0000")

Neil Jerram <neil@ossau.uklinux.net> writes:

>>>>>> "Paul" == Paul Jarc <prj@po.cwru.edu> writes:
>
>     Paul> FWIW, the definition of lazy-handler-distpatch itself
>     Paul> already looks a lot like that lambda.  It appears that you
>     Paul> can set default-lazy-handler inside the REPL to get the
>     Paul> desired effect.
>
> Yes, that's what I did before.  But that required a new variable
> `default-default-lazy-handler', which set me wondering what the
> original design was.

The original design might have had something to do with being able to
cut the stack at a proper level in order to get a nice backtrace
printout.  But this should have been solved later by the introduction
of start-stack.  (You still might want to check that stack cutting
works after your change.)

M



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-11-26 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 23:18 lazy-handler-dispatch and debug-on-error Neil Jerram
2003-11-13 20:51 ` Marius Vollmer
2003-11-14 21:11   ` Neil Jerram
2003-11-15  0:55     ` Marius Vollmer
2003-11-17 15:02 ` Paul Jarc
2003-11-17 21:13   ` Neil Jerram
2003-11-26 17:27     ` Mikael Djurfeldt [this message]
2003-11-27 21:03       ` Neil Jerram
2003-12-06 11:57         ` 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=xy7y8u359bo.fsf@chunk.mit.edu \
    --to=mdj@mit.edu \
    --cc=djurfeldt@nada.kth.se \
    --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).