From: Elliott Oti <elliott@elliottoti.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] The closing gap (warning: long, inflammatory rant)
Date: Mon, 21 Apr 2008 18:26:54 +0200 [thread overview]
Message-ID: <480CC04E.7090900@elliottoti.com> (raw)
In-Reply-To: <20080421131151.GA16777@annexia.org>
Richard Jones wrote:
> OCaml supports fork, event channels & shared memory right now
> (and has done for years) so there is no penalty to writing it
> properly.
>
Not on Win32. I use Solaris at work and Linux at home, but Win32 is a
big platform - the biggest there is right now - and the Unix module
process- and signal-related implementations there are unusable.
next prev parent reply other threads:[~2008-04-21 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 12:27 Berke Durak
2008-04-21 13:11 ` Richard Jones
2008-04-21 13:29 ` Berke Durak
2008-04-21 14:44 ` Jon Harrop
2008-04-21 20:47 ` Richard Jones
2008-04-21 21:06 ` Arnaud Spiwack
2008-04-21 21:16 ` Berke Durak
2008-04-21 23:06 ` Jon Harrop
2008-05-17 22:03 ` Jon Harrop
2008-04-21 16:26 ` Elliott Oti [this message]
2008-04-21 20:48 ` Richard Jones
2008-04-21 21:06 ` Jon Harrop
2008-04-21 14:59 ` Dario Teixeira
2008-04-21 15:57 ` Berke Durak
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=480CC04E.7090900@elliottoti.com \
--to=elliott@elliottoti.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;
as well as URLs for NNTP newsgroup(s).