From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Generators/iterators and lazy evaluation?
Date: Thu, 5 Apr 2007 07:16:52 +1000 [thread overview]
Message-ID: <20070405071652.bcb9be46.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <46140EB5.50700@inria.fr>
Alain Frisch wrote:
> I think you cannot implement this notion of iterator without some kind
> of control flow operator (at runtime) or some code rearrangement (at
> compile time). The point is that you must mainting several active
> "threads" of computations, including their own stack.
Alain, I think you may have misunderstood Python's yeild operator.
Typically the original poster's pow2 generators would be used like:
for p = pow2 (10):
print p
but I really don't see how laziness Python's generators actually
provide any benefit for this problem over the more obvious Python
solution to this which is:
for i = range (10):
p = 2 ^ i
print p
The problem with the above is that generators (and laziness in Ocaml)
really only make sense for sequences which are effecitvely infinite.
In the Python case, that would be:
def pow2 ():
start = 0
yield 2^start
start += 1
One ocaml solution to this is an class/object:
class pow2gen =
object
val mutable current = 0
method next () =
current <-
if current == 0 then 1
else current * 2 ;
current
end
which can be used like this:
let _ =
let pow2 = new pow2gen in
for k = 0 to 10 do
Printf.printf "%d : %d\n" k (pow2#next ()) ;
done
There would also be a lazy solution to this problem but I don't think
it would be a better solution that the object soultion above.
I've got a more realistic example of lazy lists on my blog:
http://www.mega-nerd.com/erikd/Blog/CodeHacking/Ocaml/lazy_lists.html
Hope this helps,
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"Every time microshaft's stock price drops again, I rejoice. I
want to see that bunch of criminals brought to their knees.
Preferably at the chopping block."
-- rixt in http://linuxtoday.com/stories/20659_flat.html
next prev parent reply other threads:[~2007-04-04 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 16:33 Raj B
2007-04-04 20:10 ` [Caml-list] " Mathias Kende
2007-04-04 20:46 ` Alain Frisch
2007-04-04 21:16 ` Erik de Castro Lopo [this message]
2007-04-04 21:37 ` Erik de Castro Lopo
2007-04-04 22:55 ` Bill Wood
2007-04-05 2:49 ` skaller
2007-04-05 16:41 ` Richard Jones
2007-04-04 23:53 ` Jon Harrop
2007-04-05 3:13 ` Erik de Castro Lopo
2007-04-05 5:58 ` Alain Frisch
2007-04-05 20:35 ` Jon Harrop
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=20070405071652.bcb9be46.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.com \
--cc=caml-list@yquem.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