Re: I/O - exception handling

[Hyman Rosen <hyrosen@mail.com>]

Warren W. Gay VE3WWG wrote:
 > If the underlying fclose() fails this could represent
 > a variety of serious program flaws and/or media defects:

It could represent Martians shooting rayguns at your disk,
too. My point is that there's absolutely nothing you can
do about it except perhaps trying to recreate the entire
file.

> I think raising exceptions in close makes sense

The problem is that if you're doing close in finalization,
allowing an exception to escape leads to program termination
in C++ and raising Program_Error in Ada. That's why you have
dual-mode closing, with an explicit close request that you
can check for error, and an automatic close in finalization
where you ignore the error.