From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id LAA01456 for caml-redistribution; Thu, 12 Aug 1999 11:50:55 +0200 (MET DST) 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 RAA12037 for ; Fri, 30 Jul 1999 17:33:03 +0200 (MET DST) Received: from iggy.triode.net.au (iggy.triode.net.au [203.63.235.1]) by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id RAA18147 for ; Fri, 30 Jul 1999 17:32:58 +0200 (MET DST) Received: from egret (pm1-4.triode.net.au [203.63.235.20]) by iggy.triode.net.au (8.9.3/8.8.8) with SMTP id BAA02385; Sat, 31 Jul 1999 01:32:07 +1000 Message-Id: <3.0.6.32.19990731012213.0098dcf0@mail.triode.net.au> X-Sender: skaller@mail.triode.net.au X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sat, 31 Jul 1999 01:22:13 +1000 To: "David McClain" , From: John Skaller Subject: Re: Finalization of I/O Channels In-Reply-To: <000101bed925$88815ff0$210148bf@dylan> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: weis At 11:17 28/07/99 -0700, David McClain wrote: >In attempting to provide finalizable I/O channels to my users, I discovered >that OCAML 2.02 is already finalizing them... But in so doing you do not >flush or close the file descriptors. Is this an oversight, or is there some >good reason for not doing so? Perhaps worse, I found that explicitly closing a file does not always work. I do not understand why, but this is surely a bug. This occured in the bytecode interpreter, and went away in with the native code compiler. [A program that wrote a file could not read it after closing the output file and reopening it input] ------------------------------------------------------- John Skaller email: skaller@maxtal.com.au http://www.maxtal.com.au/~skaller phone: 61-2-96600850 snail: 10/1 Toxteth Rd, Glebe NSW 2037, Australia