From: Brian Hurt <bhurt@spnz.org>
To: Nicolas Cannasse <warplayer@free.fr>
Cc: Pierre Weis <pierre.weis@inria.fr>,
Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>,
<caml-list@inria.fr>
Subject: Re: [Caml-list] Python's yield, Lisp's call-cc or C's setjmp/longjmp in OCaml
Date: Thu, 18 Dec 2003 01:05:20 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0312180103200.339-100000@localhost.localdomain> (raw)
In-Reply-To: <004c01c3c504$62407b80$0274a8c0@PWARP>
On Thu, 18 Dec 2003, Nicolas Cannasse wrote:
> > [...]
> > > This only works for simple examples. Try for example writing a
> > > function which successively yields all possible moves for a chess
> > > board. The "yield" operator really helps there.
> >
> > Very interesting: please give us the code corresponding to this
> > example, in order for us to realize how the full power of the "yield"
> > operator helps to solve this problem.
> >
> > Pierre Weis
> >
>
> One simple sample is tree walking :
[snip example of a usefull yield]
> Doing it using a closure is more difficult, since we need to reproduce the
> stack using a data structure. That goes of course for all recursive data
> structures.
>
Stupid question: would it be possible/usefull to have the yielding
function run as a seperate thread of execution, in a produce/consumer sort
of way?
--
"Usenet is like a herd of performing elephants with diarrhea -- massive,
difficult to redirect, awe-inspiring, entertaining, and a source of
mind-boggling amounts of excrement when you least expect it."
- Gene Spafford
Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-12-18 6:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 13:13 Nuutti Kotivuori
2003-12-16 13:28 ` Oleg Trott
2003-12-18 0:15 ` Nuutti Kotivuori
2003-12-16 13:48 ` Ville-Pertti Keinonen
2003-12-16 15:41 ` Kenneth Knowles
2003-12-16 16:45 ` Richard Jones
2003-12-16 18:36 ` Ville-Pertti Keinonen
2003-12-16 18:42 ` Brian Hurt
2003-12-16 18:10 ` Dustin Sallings
2003-12-17 6:30 ` ijtrotts
2003-12-17 8:13 ` Dustin Sallings
2003-12-17 10:35 ` Falk Hueffner
2003-12-17 19:14 ` Pierre Weis
2003-12-17 19:32 ` Falk Hueffner
2003-12-17 20:04 ` David Brown
2003-12-18 1:14 ` Nicolas Cannasse
2003-12-18 5:31 ` David Brown
2003-12-18 7:05 ` Brian Hurt [this message]
2003-12-18 6:45 ` David Brown
2003-12-18 18:44 ` brogoff
2003-12-17 19:42 ` brogoff
2003-12-19 13:39 ` skaller
2003-12-18 0:51 ` Nuutti Kotivuori
2003-12-16 18:06 Kevin S. Millikin
2003-12-18 22:08 Ker Lutyn
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=Pine.LNX.4.44.0312180103200.339-100000@localhost.localdomain \
--to=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=falk.hueffner@student.uni-tuebingen.de \
--cc=pierre.weis@inria.fr \
--cc=warplayer@free.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