Re: Alternative to System.runFinalizersOnExit()?
Twisted wrote:
Thomas Hawtin wrote:
Presumably it depends upon implementation. For a FileOutputStream
presumably there can still be work there to do that may fail. I guess
it's a "quality of implementation" matter as to whether such failures
are reported. I know not which implementations fall into which camp.
For an output stream I can see it, if there's a writeback cache to
flush to disk as part of the close and you want to report any failure
there back to the caller (e.g. by throwing an IOException).
I don't see closing an input stream (as long as it was *purely* an
input stream) blocking though, in any sensible implementation. :)
Actually, I think you might have been right for most significant
(desktop) operating systems. In C there is the issue of flushing the
buffer at an application level. At the OS level, I suspect close may
work asynchronously. It's not like sync works on most hard drives these
days anyway (performance figures are better if they are fast and loose).
But don't quote me on that.
Tom Hawtin