From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id JAA13026; Tue, 27 Jul 2004 09:41:27 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id JAA13736 for ; Tue, 27 Jul 2004 09:41:26 +0200 (MET DST) Received: from yquem.inria.fr (yquem.inria.fr [128.93.8.37]) by nez-perce.inria.fr (8.12.10/8.12.10) with ESMTP id i6R7fJEV016563; Tue, 27 Jul 2004 09:41:19 +0200 Received: by yquem.inria.fr (Postfix, from userid 18180) id 9B24FBC78; Tue, 27 Jul 2004 09:41:19 +0200 (CEST) Date: Tue, 27 Jul 2004 09:41:19 +0200 From: Xavier Leroy To: yminsky@cs.cornell.edu Cc: Caml Mailing List Subject: Re: [Caml-list] Re: Size limitation on input_value Message-ID: <20040727074119.GB18770@yquem.inria.fr> References: <891bd33904072212415292635c@mail.gmail.com> <891bd33904072609484169f951@mail.gmail.com> <20040726171205.GD6618@yquem.inria.fr> <891bd33904072611144e47e57e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <891bd33904072611144e47e57e@mail.gmail.com> User-Agent: Mutt/1.3.28i X-Miltered: at nez-perce with ID 4106071F.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 buffer:01 ocaml:01 caml:01 caml:01 blocking:01 toplevel:01 toplevel:01 maximal:02 string:03 string:03 data:03 compiled:05 intermediate:05 output:05 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk > Interesting. I can't replicate this on a stock ocaml toplevel. It > does occur, however, on a toplevel with vmthreads compiled in. Ah, you should have said that earlier. With vmthreads, input_value and output_value go through an intermediate buffer which is a Caml string (this is required because vmthreads must avoid blocking I/O system calls, hence all I/O must be performed at the Caml level). So, the size of the data written by output_value or read by input_value is limited by the maximal length of a Caml string. This limitation of vmthreads isn't new in 3.08, it's been present from the beginning. - Xavier Leroy ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners