caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>,
	caml <caml-list@inria.fr>
Subject: Re: [Caml-list] Generation of streams is slow
Date: Sat, 14 Jul 2001 14:59:40 -0700	[thread overview]
Message-ID: <3B50C0CC.811F9560@quasar.ipa.nw.ru> (raw)
In-Reply-To: <20010714210228.B2256@verdot.inria.fr>



Daniel de Rauglaudre wrote:
> 
> 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)

I don't understand, however, the argument about the order of evaluation
in _this_ case, that is of h::(make_tail args). The value of `h' is
supposed to be computed to this point, and whatever side effects are
present in `make_tail', they cannot influence the result of ::, which is
context-independent. The only difference might be the exceptions, which
can appear in `make_tail' and propagate somewhere, but the result will
not be returned anyway (the call to :: is supposed to be the _last_), so
it doesn't matter if :: is prepared to accept it or not.

Or to introduce a special version of ::, say :!:, which ensures that the
call to make_tail is really the last.

Alexander
-------------------
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


  parent reply	other threads:[~2001-07-14 22:01 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
2001-07-14 19:51                 ` Alexander V. Voinov
2001-07-14 21:59                 ` Alexander V. Voinov [this message]
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=3B50C0CC.811F9560@quasar.ipa.nw.ru \
    --to=avv@quasar.ipa.nw.ru \
    --cc=caml-list@inria.fr \
    --cc=daniel.de_rauglaudre@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;
as well as URLs for NNTP newsgroup(s).