From: Florian Weimer <fw@deneb.enyo.de>
To: "Till Varoquaux" <till.varoquaux@gmail.com>
Cc: forum@x9c.fr, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [ANN] OCaml-Java project: 1.0 release
Date: Tue, 27 May 2008 19:59:47 +0200 [thread overview]
Message-ID: <87k5hf1vcc.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <9d3ec8300805270136w75102bci903324b0ee8bb846@mail.gmail.com> (Till Varoquaux's message of "Tue, 27 May 2008 09:36:46 +0100")
* Till Varoquaux:
> Anyways; here goes for trampolines (straight from wikipedia):
>
> "Used in some LISP implementations, a trampoline is a loop that
> iteratively invokes thunk-returning functions. A single trampoline is
> sufficient to express all control transfers of a program; a program so
> expressed is trampolined or in "trampolined style"; converting a
> program to trampolined style is trampolining. Trampolined functions
> can be used to implement tail recursive function calls in
> stack-oriented languages."
I'm not sure if this is this a universally understood term. In GHC
land, this is called a "mini-interpreter". The mini-interpreter doesn't
have to be *that* expensive if you can avoid consing, but this seems to
require whole-program analysis (or, at the very least, rather powerful
inter-procedural escape analysis).
I think I've heard this term mostly in the context of currying
(specifically, in the implementation of downward closures in languages
such as Ada).
next prev parent reply other threads:[~2008-05-27 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 5:46 forum
2008-05-27 6:06 ` [Caml-list] " Jon Harrop
2008-05-27 6:37 ` Till Varoquaux
2008-05-27 7:01 ` Jon Harrop
2008-05-27 7:57 ` Till Varoquaux
2008-05-27 7:26 ` forum
2008-05-27 8:36 ` Till Varoquaux
2008-05-27 17:59 ` Florian Weimer [this message]
2008-05-27 18:57 ` forum
2008-05-27 7:23 ` forum
2008-05-27 9:12 ` Richard Jones
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k5hf1vcc.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=caml-list@yquem.inria.fr \
--cc=forum@x9c.fr \
--cc=till.varoquaux@gmail.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