Version française
Home     About     Download     Resources     Contact us    
Browse thread
Finalization of I/O Channels
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: John Skaller <skaller@m...>
Subject: Re: Finalization of I/O Channels
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