From: John Skaller <skaller@maxtal.com.au>
To: "David McClain" <dmcclain@azstarnet.com>, <caml-list@inria.fr>
Subject: Re: Finalization of I/O Channels
Date: Sat, 31 Jul 1999 01:22:13 +1000 [thread overview]
Message-ID: <3.0.6.32.19990731012213.0098dcf0@mail.triode.net.au> (raw)
In-Reply-To: <000101bed925$88815ff0$210148bf@dylan>
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
prev parent reply other threads:[~1999-08-12 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-28 18:17 David McClain
1999-07-30 15:22 ` John Skaller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.6.32.19990731012213.0098dcf0@mail.triode.net.au \
--to=skaller@maxtal.com.au \
--cc=caml-list@inria.fr \
--cc=dmcclain@azstarnet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox