From: skaller <skaller@users.sourceforge.net>
To: Zheng Li <li@pps.jussieu.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: [ANN] coThreads 0.10
Date: Tue, 18 Sep 2007 09:26:40 +1000 [thread overview]
Message-ID: <1190071600.22073.7.camel@rosella.wigram> (raw)
In-Reply-To: <873axc7wan.fsf@pps.jussieu.fr>
On Tue, 2007-09-18 at 00:37 +0200, Zheng Li wrote:
> For immutable value, it's not different from the traditional threads, at least
> from the library users' point of view: if a variable is already inside the
> scope of a threads (i.e. it's global and created before launching the thread),
> there is no necessity to message passing it; if not, you should anyway do it
> explicitly even with the traditional threads.
Yes, however such a value can't be shared by parallel control paths
(in ocaml) because the collector won't allow it. Of course
you can *copy* it eg with fork() and run separate collectors.
Then the functional value is the same, but the object identity
(machine address) may differ.
BTW: an interesting application would be to adapt GLR parser
to actually use multi-core CPU to speed up parsing by spawning
alternate parses as parallel control streams.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-09-17 23:26 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 16:31 Zheng Li
2007-09-17 16:48 ` Zheng Li
2007-09-17 17:39 ` [Caml-list] " skaller
2007-09-17 17:51 ` Zheng Li
2007-09-17 21:33 ` [Caml-list] " skaller
2007-09-17 22:37 ` Zheng Li
2007-09-17 23:26 ` skaller [this message]
2007-09-18 0:16 ` Zheng Li
2007-09-18 0:53 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 1:25 ` Erik de Castro Lopo
2007-09-18 4:29 ` skaller
2007-09-19 10:11 ` Erik de Castro Lopo
2007-09-19 10:58 ` Can coThreads be used for message passing architecture? Jan Kybic
2007-09-19 11:13 ` [Caml-list] " Erik de Castro Lopo
2007-09-19 12:59 ` Zheng Li
2007-09-20 4:16 ` [Caml-list] " Jon Harrop
2007-09-20 6:11 ` Erik de Castro Lopo
2007-09-20 9:06 ` Zheng Li
2007-09-20 8:49 ` Zheng Li
2007-09-19 19:13 ` [Caml-list] Re: [ANN] coThreads 0.10 Vu Ngoc San
2007-09-19 20:10 ` Zheng Li
2007-09-20 0:50 ` [Caml-list] " skaller
2007-09-20 4:29 ` Erik de Castro Lopo
2007-09-20 7:11 ` skaller
2007-09-20 7:52 ` Erik de Castro Lopo
2007-09-20 8:37 ` Zheng Li
2007-09-20 10:43 ` [Caml-list] " skaller
2007-09-20 10:44 ` Matthew Hannigan
2007-09-20 15:02 ` skaller
2007-09-20 15:07 ` Christophe Raffalli
2007-09-20 15:51 ` skaller
2007-09-20 16:26 ` Florian Weimer
2007-09-20 17:37 ` Vincent Aravantinos
2007-09-21 16:33 ` readline license (was: [ANN] coThreads 0.10) Xavier Leroy
2007-09-21 17:11 ` [Caml-list] " Matthew William Cox
2007-09-21 18:05 ` skaller
2007-09-21 21:51 ` [Caml-list] Re: readline license Markus E L
2007-09-21 22:16 ` Daniel Bünzli
2007-09-22 0:49 ` [Caml-list] Re: readline license (was: [ANN] coThreads 0.10) Matthew Hannigan
2007-09-20 11:39 ` [Caml-list] Re: [ANN] coThreads 0.10 Florian Weimer
2007-09-20 15:46 ` skaller
2007-09-20 18:14 ` Ken Rose
2007-09-20 8:31 ` Zheng Li
2007-09-20 8:18 ` Zheng Li
2007-09-18 2:10 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 5:59 ` skaller
2007-09-18 6:23 ` Erik de Castro Lopo
2007-09-18 9:01 ` Zheng Li
2007-09-18 13:40 ` Zheng Li
2007-09-18 23:53 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 9:09 ` [Caml-list] " skaller
2007-09-18 13:03 ` Markus E L
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=1190071600.22073.7.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=li@pps.jussieu.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).