From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <forsyth@terzarima.net>
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled 
	version=3.1.3
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by yquem.inria.fr (Postfix) with ESMTP id 1755BBBCA
	for <caml-list@yquem.inria.fr>; Sun, 11 May 2008 11:36:03 +0200 (CEST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAKJaJkhQRF4M/2dsb2JhbACpaA
X-IronPort-AV: E=Sophos;i="4.27,468,1204498800"; 
   d="scan'208";a="10592771"
Received: from verso.terzarima.net ([80.68.94.12])
  by mail2-smtp-roc.national.inria.fr with ESMTP; 11 May 2008 11:36:02 +0200
Message-ID: <b3fc86ed737ea8ceb6d9cfce0eaa6d9c@terzarima.net>
To: jon@ffconsultancy.com, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: Why OCaml rocks
From: Charles Forsyth <forsyth@terzarima.net>
Date: Sun, 11 May 2008 10:41:06 +0100
In-Reply-To: <200805110458.19162.jon@ffconsultancy.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam: no; 0.00; ocaml:01 forsyth:01 forsyth:01 ocaml:01 deallocation:01 caml-list:01 shared:06 referencing:07 blocks:07 manually:08 alternatives:08 memory:09 complicated:09 obvious:10 difficult:13 

> Copying is the obvious solution in OCaml because there is no easy way to share 
> OCaml values between processes.

>There are alternatives (like referencing shared memory as custom blocks and 
>managing deallocation manually) but they are substantially more complicated 

ok, i understand now: it would be possible in principle given the language,
but current implementation makes it difficult.