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 QAA12629; Thu, 11 Mar 2004 16:17:21 +0100 (MET) 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 QAA11538 for ; Thu, 11 Mar 2004 16:17:20 +0100 (MET) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by nez-perce.inria.fr (8.12.10/8.12.10) with ESMTP id i2BFHbKW002639 for ; Thu, 11 Mar 2004 16:17:38 +0100 Received: from [192.168.1.200] (ppp114-118.lns1.syd3.internode.on.net [150.101.114.118]) by smtp3.adl2.internode.on.net (8.12.9/8.12.9) with ESMTP id i2BFH2UK085207; Fri, 12 Mar 2004 01:47:08 +1030 (CST) Subject: Re: [Caml-list] Bug with really_input under cygwin From: skaller Reply-To: skaller@users.sourceforge.net To: Nuutti Kotivuori Cc: skaller@users.sourceforge.net, caml-list@pauillac.inria.fr In-Reply-To: <87znao0ydf.fsf@aka.i.naked.iki.fi> References: <51FE3429-7219-11D8-8BF5-000393914EAA@atcorp.com> <1078888018.2452.52.camel@pelican.wigram> <87hdww4tc9.fsf@aka.i.naked.iki.fi> <1078976542.2452.106.camel@pelican.wigram> <87znao0ydf.fsf@aka.i.naked.iki.fi> Content-Type: text/plain Message-Id: <1079018473.2452.174.camel@pelican.wigram> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) Date: 12 Mar 2004 02:21:14 +1100 Content-Transfer-Encoding: 7bit X-Miltered: at nez-perce by Joe's j-chkmail ("http://j-chkmail.ensmp.fr")! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 bug:01 cygwin:01 sourceforge:01 2004:99 sourceforge:01 portably:01 abstraction:01 abstractions:01 non-blocking:01 9660:01 glebe:01 ocaml:01 nsw:01 snail:02 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk X-Status: X-Keywords: X-UID: 116 On Thu, 2004-03-11 at 16:02, Nuutti Kotivuori wrote: > skaller@users.sourceforge.net wrote: > But - there's nothing ambiguous about slurping an entire file into a > string. And there's nothing complex about doing that portably. A file is an abstraction, meaning it is a collection of access methods. There's no 'bytes' in a file, the bytes are just values return from the read function or submitted to the write function. Many files exist with many different access methods. Even the same physical disk data can be different file abstractions: eg Unix directory. The data on an unbuffered non-blocking serial communication link cannot be read with the block reading algorithm I gave: end of data occurs before end of file -- if there is an end of file .. eg it won't work on a raw terminal. Yes, I know we have strayed a long way from the original question, but I think the issue here is: the manual isn't precise enough, but making it so is in fact very difficult, so the Ocaml team is 'forgiven'. That's what I think I was trying to say :D -- John Skaller, mailto:skaller@users.sf.net voice: 061-2-9660-0850, snail: PO BOX 401 Glebe NSW 2037 Australia Checkout the Felix programming language http://felix.sf.net ------------------- 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