From: "Corey O'Connor" <coreyoconnor@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] Threads question...
Date: Mon, 19 Jul 2004 15:33:20 -0700 [thread overview]
Message-ID: <c1291235040719153348f1f8c4@mail.gmail.com> (raw)
"The threads library is implemented by time-sharing on a single
processor. It will not take advantage of multi-processor machines.
Using this library will therefore never make programs run faster.
However, many programs are easier to write when structured as several
communicating processes."
However, the documentation states that the native threads library is
implemented using the system's native threading. (POSIX threads, in my
case)
Is the quote above still consistent with the native threads implementation?
--
-Corey O'Connor
-------------------
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 reply other threads:[~2004-07-19 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 22:33 Corey O'Connor [this message]
2004-07-20 7:26 ` Jacques GARRIGUE
2007-10-10 14:43 Raj Bandyopadhyay
2007-10-10 15:04 ` [Caml-list] " Daniel Bünzli
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=c1291235040719153348f1f8c4@mail.gmail.com \
--to=coreyoconnor@gmail.com \
--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