From: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Generation of streams is slow
Date: Fri, 13 Jul 2001 21:40:11 -0700 [thread overview]
Message-ID: <3B4FCD2B.FC68C181@quasar.ipa.nw.ru> (raw)
In-Reply-To: <3B4FC748.F9E14008@quasar.ipa.nw.ru>
"Alexander V. Voinov" wrote:
> > Perhaps this version would work (not tested):
> >
> > let rec parse_stream list s =
> > match s with parser
> > [< 'i; s' >] -> begin
> > if i mod 1000 = 0 then begin
> > printf "picked element %d\n" i;
> > flush stdout
> > end;
> > parse_stream (i :: list) s'
> > end
> > | [< >] -> (printf "end\n"; flush stdout; List.rev list)
>
> I see, Prolog habits are hard to leave. But this solution doesn't look
> as "natural" as mine, and requires additional time to reverse the
> result. I try to acquire hints for the everyday use, of lists and other
> abstract sequences in this case. Not just a particular problem to solve.
And in general, the inability to pass free variables to be bound later
limits the tail recursion optimization. And forces to use iterations
when they exist (as they do in OCaml).
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
next prev parent reply other threads:[~2001-07-14 4:41 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 [this message]
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
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=3B4FCD2B.FC68C181@quasar.ipa.nw.ru \
--to=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