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 DAA03241 for caml-redistribution; Fri, 30 Jul 1999 03:24:36 +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 UAA26635 for ; Wed, 28 Jul 1999 20:17:53 +0200 (MET DST) Received: from cepheus.azstarnet.com (cepheus.azstarnet.com [169.197.56.195]) by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id UAA28715 for ; Wed, 28 Jul 1999 20:17:50 +0200 (MET DST) Received: from dylan (dialup02ip049.tus.azstarnet.com [169.197.30.177]) by cepheus.azstarnet.com (8.9.3/8.9.3) with SMTP id LAA03269 for ; Wed, 28 Jul 1999 11:17:38 -0700 (MST) X-Sent-via: StarNet http://www.azstarnet.com/ Message-ID: <000101bed925$88815ff0$210148bf@dylan> From: "David McClain" To: Subject: Finalization of I/O Channels Date: Wed, 28 Jul 1999 11:17:57 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: weis 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? D.McClain