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=none autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from discorde.inria.fr (discorde.inria.fr [192.93.2.38]) by yquem.inria.fr (Postfix) with ESMTP id AE7C5BC0B for ; Wed, 17 Jan 2007 17:34:13 +0100 (CET) Received: from smtp.irisa.fr (smtp.irisa.fr [131.254.254.26]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id l0HGYDlv027087 for ; Wed, 17 Jan 2007 17:34:13 +0100 Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost.irisa.fr (Postfix) with ESMTP id 7169EFABB; Wed, 17 Jan 2007 17:34:12 +0100 (CET) Received: from smtp.irisa.fr ([131.254.254.26]) by localhost (meli.irisa.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30954-05-2; Wed, 17 Jan 2007 17:34:09 +0100 (CET) Received: from [131.254.10.144] (polaris.irisa.fr [131.254.10.144]) by smtp.irisa.fr (Postfix) with ESMTP id 3090AFA9E; Wed, 17 Jan 2007 17:34:09 +0100 (CET) Message-ID: <45AE5001.2080709@irisa.fr> Date: Wed, 17 Jan 2007 17:34:09 +0100 From: Sebastien Ferre Organization: IRISA User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: caml-list@yquem.inria.fr Cc: =?ISO-8859-1?Q?Daniel_B=FCnzli?= Subject: Re: [Caml-list] marshaling limits References: <2a1a1a0c0701161248l5a1d9ad9q739da9c593fc5219@mail.gmail.com> <45ADE8FE.5070004@irisa.fr> <45AE41C7.8080409@univ-paris12.fr> <45AE43A9.3090904@irisa.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at irisa.fr X-Miltered: at discorde with ID 45AE5005.001 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; irisa:01 marshaling:01 bunzli:01 bytecode:01 bytecode:01 wrote:01 exception:01 caml-list:01 data:02 output:02 output:02 string:02 string:02 executable:03 daniel:04 Daniel Bünzli wrote: >> pourtant, je passe bien par un appel a output_value >> dans un fichier, sans passer par une chaine intermediaire. > > Maybe output_value uses a string internally. Try with a bytecode > version of your executable, an exception should be raised (or have a > look at the implementaiton of output_value). I used a bytecode version. I checked the code of output_value, and it uses an internal string. So it won't work. Anyway, I knew I would have to go for a more serious solution as soon as data get really large. I think of using something like GDBM. Thanks for the help. Sebastien