From: Andy Wingo <wingo@pobox.com>
To: <dsmich@roadrunner.com>
Cc: guile-devel@gnu.org
Subject: Re: scm_internal_stack_catch
Date: Fri, 01 Jul 2011 12:29:27 +0200 [thread overview]
Message-ID: <87k4c28faw.fsf@pobox.com> (raw)
In-Reply-To: <20110506142104.1ZFS4.38448.root@cdptpa-web12-z02> (dsmich@roadrunner.com's message of "Fri, 6 May 2011 10:21:04 -0400")
On Fri 06 May 2011 16:21, <dsmich@roadrunner.com> writes:
> I've been slowly (very slowly!) debitrotting scwm.
Cool! I've been (very slowly!) catching up to the present with regards
to guile-devel.
> There is currently a deprecation warning for scm_internal_stack_catch.
> The warning says to talk to guile-devel. So I'm talking. ;^) What
> should this be replaced with?
Here's the deal.
1) Internal_stack_catch uses the the-last-stack fluid, which Guile no
longer has.
2) It is also a "lazy catch", meaning that it unwinds the dynamic
state to the catch, but doesn't unwind the stack. Guile doesn't
allow this any more. This may or may not have repercussions for
you.
Instead, in Guile 2.0, your best bet is to use
`call-with-error-handling'. See "Pre-Unwind Debugging" in the manual,
for more.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-07-01 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 14:21 scm_internal_stack_catch dsmich
2011-07-01 10:29 ` Andy Wingo [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=87k4c28faw.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=dsmich@roadrunner.com \
--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).