From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d8a4797a79f9c90f
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-05-27 03:31:51 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!tdsnet-transit!newspeer.tds.net!news.binc.net!kilgallen
From: Kilgallen@SpamCop.net (Larry Kilgallen)
Newsgroups: comp.lang.ada
Subject: Re: I/O - exception handling
Date: 27 May 2003 05:31:49 -0500
Organization: Berbee Information Networks Corporation
Message-ID: <yjp8G+z9TOWO@eisner.encompasserve.org>
References: <bat3ee$2ec$1@ns.felk.cvut.cz>
 <slrnbd45rq.523.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <bat7as$3oi$1@ns.felk.cvut.cz>
 <slrnbd494u.523.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <bat8vn$48r$1@ns.felk.cvut.cz>
 <slrnbd4hqk.2hh.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <batk1o$80q$1@ns.felk.cvut.cz>
 <slrnbd4m0j.4gn.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <batnhp$956$1@ns.felk.cvut.cz> <D7zAa.12988$xV3.9550@nwrdny03.gnilink.net>
 <DP0K7Hf7GLdM@eisner.encompasserve.org>
 <HcAAa.13109$xV3.2235@nwrdny03.gniliOrganization: LJK Software
NNTP-Posting-Host: eisner.encompasserve.org
X-Trace: grandcanyon.binc.net 1054031476 25909 192.135.80.34 (27 May 2003
 10:31:16 GMT)
X-Complaints-To: abuse@binc.net
NNTP-Posting-Date: Tue, 27 May 2003 10:31:16 +0000 (UTC)
Xref: archiver1.google.com comp.lang.ada:37829
Date: 2003-05-27T05:31:49-05:00
List-Id: <comp.lang.ada>

In article <HcAAa.13109$xV3.2235@nwrdny03.gnilink.net>, Hyman Rosen <hyrosen@mail.com> writes:
> The main problem is that when you get an error on closing a
> file, there's no recovery possible short of trying to recreate
> its contents somehow and somewhere. It's more like a hardware
> error than anything else.

And hardware errors are also well worth reporting to the humans.