From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: bug with call-with/cc and lambda?
Date: Tue, 23 Apr 2002 16:57:48 -0700 [thread overview]
Message-ID: <E170AAO-0006yI-00@giblet> (raw)
In-Reply-To: <20020408141116.A6050@bachue.com> (message from Alejandro Forero Cuervo on Mon, 8 Apr 2002 14:11:16 -0500)
From: Alejandro Forero Cuervo <bachue@bachue.com>
Date: Mon, 8 Apr 2002 14:11:16 -0500
However, when I do the following very similar construction, Guile
hangs but also starts to consume a lot of memory, giving me the idea
that something that could be tail-recursive somewhere isn't:
(define (f x) (call-with-current-continuation (lambda (x) (f x))))
(call-with-current-continuation f)
Shouldn't this use constant memory?
does it in other scheme implementations?
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-04-23 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 23:33 guile as extension language Matthew R Wette
2002-04-08 19:11 ` bug with call-with/cc and lambda? Alejandro Forero Cuervo
2002-04-23 23:57 ` Thien-Thi Nguyen [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=E170AAO-0006yI-00@giblet \
--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).