From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: Continuations: possible newbie question
Date: Wed, 18 Dec 2002 09:27:03 -0800 [thread overview]
Message-ID: <E18OhyJ-0008VJ-00@giblet.glug.org> (raw)
In-Reply-To: message from Matt Hellige on Tue, 17 Dec 2002 18:14:25 -0600
From: Matt Hellige <matt@immute.net>
Date: Tue, 17 Dec 2002 18:14:25 -0600
is this due to a bug in guile,
perhaps. here is what i see:
guile> (version)
"1.4.1.93"
guile> (load "cwcc.scm") ; as posted
guile> (exec-binding bind)
"escaped"
guile> (done-reading "hi")
hi
guile>
or to my abuse of continuations?
continuations are basically a sanctioned control-flow abuse mechanism,
so it is all just a matter of degree. i have been happy not to use them
except as escapes, in my code. in one gig i used them -- guile 1.3.4, i
believe -- as co-routines (like your example) but that was more to
impress the Boss (and drag myself out of ignorance ;-) than anything.
another way to do what I'm trying to do?
probably you can continue your explorations in this vein w/ more
debugging support: use `trace' and `pk' to determine where things go
wrong, and/or use a guile version that behaves as you expect.
all other ways essentially devolve into using continuations.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2002-12-18 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 17:27 Thien-Thi Nguyen [this message]
2002-12-18 18:14 ` Continuations: possible newbie question Matt Hellige
2002-12-18 20:04 ` Neil Jerram
2002-12-18 23:51 ` Matt Hellige
2002-12-19 0:41 ` Marius Vollmer
2002-12-19 2:42 ` Matt Hellige
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 18:42 Thien-Thi Nguyen
2002-12-18 0:14 Matt Hellige
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=E18OhyJ-0008VJ-00@giblet.glug.org \
--to=ttn@giblet.glug.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).