From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org
Subject: Re: manipulating continuations
Date: Sat, 12 Feb 2011 21:56:56 +0100 [thread overview]
Message-ID: <87wrl53raf.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3k4h59nrv.fsf@unquote.localdomain> (Andy Wingo's message of "Sat, 12 Feb 2011 18:16:20 +0100")
() Andy Wingo <wingo@pobox.com>
() Sat, 12 Feb 2011 18:16:20 +0100
R5RS and R6RS's continuations are not generally useful for making
abstractions that compose well together. I would not recommend them to
anyone.
Are you saying Guile 2.0 breaks code that uses these traditional
continuations (successfully, in previous Guile versions)? I think
the OP example should be in NEWS, if so, to avoid a surprise.
next prev parent reply other threads:[~2011-02-12 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 14:10 manipulating continuations Thomas Girod
2011-02-12 15:43 ` Andy Wingo
2011-02-12 16:40 ` Keith Wright
2011-02-12 17:16 ` Andy Wingo
2011-02-12 20:56 ` Thien-Thi Nguyen [this message]
2011-02-12 21:33 ` Andy Wingo
[not found] ` <1297887196-sup-8146@cresylol.hd.free.fr>
2011-02-17 11:08 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2011-02-12 8:35 Tomtom
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=87wrl53raf.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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).