From: Andy Wingo <wingo@pobox.com>
To: Thomas Girod <girodt@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: manipulating continuations
Date: Sat, 12 Feb 2011 16:43:59 +0100 [thread overview]
Message-ID: <m3oc6h9s1s.fsf@unquote.localdomain> (raw)
In-Reply-To: <4D5694ED.7080402@gmail.com> (Thomas Girod's message of "Sat, 12 Feb 2011 15:10:53 +0100")
Hi Thomas,
On Sat 12 Feb 2011 15:10, Thomas Girod <girodt@gmail.com> writes:
> (define (foo)
> (call/cc
> (lambda (return)
> (display "first part")
> (newline)
> (call/cc
> (lambda (cont)
> (return cont)))
> (display "second part")
> (newline))))
>
> guile> (define c (foo))
> first part
> guile> (c)
> second part
>
> yay, it works. But now, what if I want to run the continuation directly,
> rather than storing it and calling it later ? This is what I get:
>
> guile> ((foo))
> first part
> second part
>
> Backtrace:
> In current input:
> 15: 0* [#<unspecified>]
In this expression, `foo' has returned twice. The first time it
returned a continuation, which was applied. The second time it returned
whatever `newline' returned: the unspecified value. Applying the
unspecified value failed.
If you use Guile 1.9/2.0, partial continuations behave more in the way
you were thinking of:
(use-modules (ice-9 control))
(define (foo)
(% (begin
(display "first part\n")
(abort)
(display "second part\n"))
(lambda (cont)
;; abort jumps back here, to the handler. return the partial
;; continuation.
cont)))
scheme@(guile-user)> (foo)
first part
$1 = #<partial-continuation 29dede0>
scheme@(guile-user)> ($1)
second part
scheme@(guile-user)> ((foo))
first part
second part
scheme@(guile-user)>
Have fun with Guile,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-12 15:43 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 [this message]
2011-02-12 16:40 ` Keith Wright
2011-02-12 17:16 ` Andy Wingo
2011-02-12 20:56 ` Thien-Thi Nguyen
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=m3oc6h9s1s.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=girodt@gmail.com \
--cc=guile-user@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).