From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] concurrency using forks and pipes (some working code)
Date: Mon, 4 Jun 2007 17:51:30 +1000 [thread overview]
Message-ID: <20070604175130.9edebf8f.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <20070604071415.GF1297@yumegakanau.org>
Christopher Cramer wrote:
> Jon Harrop asked about this recently and I thought it was an interesting
> idea and implemented it:
>
> http://yumegakanau.org/blog/2007/06/03/
Is this not redundant with the recent release of JoCaml?
> (BTW I don't think you are "faking" concurrency by using fork...)
I consider concurrency with forking the correct way to do it
and concurrency with threads as "faking" it :-).
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
"TLC declared bankruptcy after they received less than 2 percent of the $175
million earned by their CD sales. That was about 40 times less than the
profit that was divided among their management, production and record
companies." -- Courtney Love on the REAL piracy
prev parent reply other threads:[~2007-06-04 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 7:14 Christopher Cramer
2007-06-04 7:51 ` Erik de Castro Lopo [this message]
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=20070604175130.9edebf8f.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.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