From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Generation of streams is slow
Date: Sat, 14 Jul 2001 21:02:28 +0200 [thread overview]
Message-ID: <20010714210228.B2256@verdot.inria.fr> (raw)
In-Reply-To: <3B508A89.82717B26@quasar.ipa.nw.ru>; from avv@quasar.ipa.nw.ru on Sat, Jul 14, 2001 at 11:08:09AM -0700
Hi,
On Sat, Jul 14, 2001 at 11:08:09AM -0700, Alexander V. Voinov wrote:
> h::(make_tail arg1 argN),
> that is
> CALL make_tail
> CONS
> and change them to
> PREPARE_CONS
> CALL make_tail
> the scope of tail recursion optimization would increase. But it's
> unlikely that this idea didn't come to developers. Which may mean that
> this [being not that simple] is impossible.
It supposes that the order of evaluation could be variable. If we
imagine a constructor C with 5 parameters. If we evalutate:
C (a, b, c, d, e)
Here, the order of evaluation is a-b-c-d-e or e-d-c-b-a, I don't know,
but in some logical order. If the tail recursion is, say, on the third
parameter c, it supposes that a, b, d and e be evaluated before. And
what policy use if, say, d is another tail recursion?
In OCaml the evaluation order is not - supposed to be - specified. In
this case, it would less be specified, since it could change depending
on the parameters. Interesting... But I don't know if it is possible to
implement that in the code generation.
--
Daniel de RAUGLAUDRE
daniel.de_rauglaudre@inria.fr
http://cristal.inria.fr/~ddr/
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-07-14 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 22:06 Alexander V. Voinov
2001-07-14 2:27 ` Daniel de Rauglaudre
2001-07-14 2:51 ` Alexander V. Voinov
2001-07-14 4:04 ` Daniel de Rauglaudre
2001-07-14 4:15 ` Alexander V. Voinov
2001-07-14 4:40 ` Alexander V. Voinov
2001-07-14 8:34 ` Daniel de Rauglaudre
2001-07-14 18:08 ` Alexander V. Voinov
2001-07-14 19:02 ` Daniel de Rauglaudre [this message]
2001-07-14 19:51 ` Alexander V. Voinov
2001-07-14 21:59 ` Alexander V. Voinov
2001-07-14 22:29 ` Daniel de Rauglaudre
2001-07-17 2:36 ` Jacques Garrigue
2001-07-14 8:31 ` Daniel de Rauglaudre
2001-07-20 7:49 ` Chris Hecker
2001-07-17 16:01 Dave Berry
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=20010714210228.B2256@verdot.inria.fr \
--to=daniel.de_rauglaudre@inria.fr \
--cc=avv@quasar.ipa.nw.ru \
--cc=caml-list@inria.fr \
/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