From: Matt Wette <matt.wette@gmail.com>
To: 21897@debbugs.gnu.org
Subject: bug#21897: verified in 3.0.2
Date: Sun, 29 Mar 2020 10:28:36 -0700 [thread overview]
Message-ID: <5699d998-480a-0f0d-ee59-c44100c2e6d2@gmail.com> (raw)
In-Reply-To: <20151113033126.GA16544@fysh.org>
This still exists in 3.0.2
scheme@(guile-user)> ,use (ice-9 control)
scheme@(guile-user)> (call/ec (lambda (c) (with-continuation-barrier (lambda () (c "through continuation"))) "c-w-b returned"))
$1 = "through continuation"
scheme@(guile-user)> (version)
$2 = "3.0.2"
prev parent reply other threads:[~2020-03-29 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 3:31 bug#21897: escape continuation passes barrier Zefram
2016-06-24 16:23 ` Andy Wingo
2020-03-29 17:28 ` Matt Wette [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=5699d998-480a-0f0d-ee59-c44100c2e6d2@gmail.com \
--to=matt.wette@gmail.com \
--cc=21897@debbugs.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).