From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id 015A4BB9C for ; Fri, 25 Nov 2005 21:06:01 +0100 (CET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id jAPK61bc009274 for ; Fri, 25 Nov 2005 21:06:01 +0100 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id VAA17866 for ; Fri, 25 Nov 2005 21:06:01 +0100 (MET) Received: from mx1.mail.ru (mx1.mail.ru [194.67.23.121]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id jAPK5xV6006607 for ; Fri, 25 Nov 2005 21:06:00 +0100 Received: from [195.245.255.11] (port=11873 helo=bely) by mx1.mail.ru with asmtp id 1EfjpR-0009lk-00 for caml-list@inria.fr; Fri, 25 Nov 2005 23:05:59 +0300 Received: from localhost (HELO BELY) [127.0.0.1] by bely (0.0.0.1) with ESMTP (Classic Hamster Vr. 2.0 Build 2.0.0.1) ; Fri, 25 Nov 2005 23:06:40 +0300 X-Comment-To: Thomas Fischbacher To: caml-list@inria.fr Subject: Re: [Caml-list] Bigarray question References: From: Dmitry Bely Date: Fri, 25 Nov 2005 23:06:40 +0300 In-Reply-To: (Thomas Fischbacher's message of "Fri, 25 Nov 2005 19:19:14 +0100 (CET)") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.5 (chayote, windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: Hamster/2.0.0.1 X-Miltered: at nez-perce with ID 43876EA9.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at concorde with ID 43876EA7.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 bigarray:01 bigarray:01 pointer:01 pointer:01 externally:01 alloc:01 writes:01 dmitry:01 dmitry:01 explicitly:01 bely:02 bely:02 dbely:02 data:02 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 Thomas Fischbacher writes: > As far as I can see from the documentation, it is not explicitly permitted > to change a once allocated bigarray data structure in such a way that one > replaces the data pointer by some other data pointer (while retaining > size and type). This would, however, be quite useful in some situations. Is your bigarray a wrapper around some externally allocated data, created via alloc_bigarray() C call? If yes, you can safely replace the data pointer with another one via Caml-C interface. If not, why do you need that? - Dmitry Bely