caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] forking, threads and events
Date: Wed, 11 Oct 2006 10:23:35 +1000	[thread overview]
Message-ID: <20061011102335.d960782b.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <1160483909.32409.35.camel@localhost.localdomain>

Gerd Stolpmann wrote:

> You know that there is no fork on Windows?

Yeah, but I was thinking of using the Cygwin version which I 
think does have fork (and select which is also missing).

> If there wasn't the Windows requirement I could recommend this:
> 
> You may have a look at ocamlnet2. It includes the netplex library that
> manages parent/children relationships between either forked processes or
> threads. You can use SunRPC for communication (or whatever you like, but
> SunRPC support is included). The bad news is that it does not run on the
> native Windows port, not even in the threaded variant (because there's
> no socketpair...).

I hate windows. There are so many good, reliable, well designed
OSes out there and people on those good OSes still have to work
around the fact the the vast majority of people are on a broken
piece of crap like windows.

Erik
-- 
+-----------------------------------------------------------+
  Erik de Castro Lopo
+-----------------------------------------------------------+
The main confusion about C++ is that its practitioners think
it is simultaneously a  high and low level language when in
reality it is good at neither.


  reply	other threads:[~2006-10-11  0:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 12:16 Erik de Castro Lopo
2006-10-10 12:38 ` [Caml-list] " Gerd Stolpmann
2006-10-11  0:23   ` Erik de Castro Lopo [this message]
     [not found] ` <1160490322.16459.110.camel@rosella.wigram>
2006-10-11  0:22   ` Erik de Castro Lopo

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=20061011102335.d960782b.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;
as well as URLs for NNTP newsgroup(s).