Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!ukma!nrl-cmf!ames!hao!oddjob!gargoyle!ihnp4!homxb!mtuxo!mtune!codas!burl!clyde!watmath!orchid!atbowler
From: atbowler@orchid.waterloo.edu (Alan T. Bowler [SDG])
Newsgroups: comp.lang.c
Subject: Re: stdio error detection
Message-ID: <11910@orchid.waterloo.edu>
Date: Mon, 30-Nov-87 13:20:40 EST
Article-I.D.: orchid.11910
Posted: Mon Nov 30 13:20:40 1987
Date-Received: Fri, 4-Dec-87 03:18:17 EST
References: <289@cresswell.quintus.UUCP> <6748@brl-smoke.ARPA> <290@cresswell.quintus.UUCP>
Reply-To: atbowler@orchid.waterloo.edu (Alan T. Bowler [SDG])
Organization: U. of Waterloo, Ontario
Lines: 8
Keywords: errno fclose fopen stdio errors

Complete error handling is intrinsically OS and machine dependent.
If you are worried about a bullet proof portable solution, then
you define your own cover functions for fopen(), fclose() etc
with the semantics you want.  Typically, these will be 5-20 lines of code.
Then as part of the porting exercise for the program, you code an
implementation specific versions of the functions making use of the
implementation documentation of how these things can fail, and how
you detect this.