From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: srfi-13 string-any tail call
Date: Thu, 23 Dec 2004 08:30:29 +1100 [thread overview]
Message-ID: <87r7likolm.fsf@zip.com.au> (raw)
In-Reply-To: <ljwtvab7ei.fsf@troy.dt.e-technik.uni-dortmund.de> (Marius Vollmer's message of "Wed, 22 Dec 2004 17:54:29 +0100")
Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>
> Yes. It would be nice in general to have a new kind of 'trampoline'
> subr that returns a function+args to call in a tail-recursive way.
Or func+args in some new magic type, so a subr can return either a
value or a new place to goto.
I was wanting `catch' to do a tail call to its handler so the handler
could recurse to continue on the rest of some data. `catch' would be
a case of either returning a value (from the body) or the handler to
jump to.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-12-22 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 21:08 srfi-13 string-any tail call Kevin Ryde
2004-12-22 16:54 ` Marius Vollmer
2004-12-22 21:30 ` Kevin Ryde [this message]
2004-12-23 4:16 ` Marius Vollmer
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=87r7likolm.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).