From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id A769DBC69 for ; Wed, 19 Dec 2007 18:47:18 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAC/naEfUGyokimdsb2JhbACPfwEBAQgEBiIHmhM X-IronPort-AV: E=Sophos;i="4.24,185,1196636400"; d="scan'208";a="5835503" Received: from discorde.inria.fr ([192.93.2.38]) by mail1-smtp-roc.national.inria.fr with ESMTP; 19 Dec 2007 18:47:18 +0100 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id lBJHlIms013185 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Wed, 19 Dec 2007 18:47:18 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAC/naEfUGyokimdsb2JhbACPfwEBAQgEBiIHmhM X-IronPort-AV: E=Sophos;i="4.24,185,1196636400"; d="scan'208";a="5835502" Received: from smtp6-g19.free.fr ([212.27.42.36]) by mail1-smtp-roc.national.inria.fr with ESMTP; 19 Dec 2007 18:47:18 +0100 Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp6-g19.free.fr (Postfix) with ESMTP id 000745FEF8; Wed, 19 Dec 2007 18:47:17 +0100 (CET) Received: from [192.168.1.3] (che78-2-82-237-71-191.fbx.proxad.net [82.237.71.191]) by smtp6-g19.free.fr (Postfix) with ESMTP id 9F32D5FEDE; Wed, 19 Dec 2007 18:47:17 +0100 (CET) Message-ID: <47695924.8090202@inria.fr> Date: Wed, 19 Dec 2007 18:47:16 +0100 From: Xavier Leroy User-Agent: Thunderbird 2.0.0.4 (X11/20070620) MIME-Version: 1.0 To: Thomas Fischbacher Cc: Caml-list List Subject: Re: [Caml-list] Bigarray question References: <476806F9.4030100@functionality.de> In-Reply-To: <476806F9.4030100@functionality.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Miltered: at discorde with ID 47695926.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; bigarray:01 bigarray:01 pointer:01 pointer:01 caml-list:01 explicitly:02 explicitly:02 data:02 data:02 caml:02 shape:96 problem:05 xavier:06 xavier:06 inria:06 > as far as I can tell, it is easy (but not explicitly allowed in the > documentation) to allocate a Caml bigarray and change the data > pointer inside that bigarray afterwards. > There is no problem in implementing this, technically speaking. > But this would require a change to the ML documentation stating > that it is explicitly considered as permissible to change the > data pointer in a bigarray. Can I get that, please? I see no reason why this would cause problems, as long as the data pointer points to C data of the right shape and dimensions. (Of course, you could update the dimensions of the bigarray as appropriate, if needed.) I don't think I would document this, as I wouldn't quite know how to word it in the docs, but you have my encouragements to try and report problems if any. - Xavier Leroy