Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ames!oliveb!pyramid!prls!philabs!ttidca!quad1!oleg From: oleg@quad1.quad.com (Oleg Kiselev) Newsgroups: comp.lang.c Subject: Re: stdio error detection Message-ID: <1347@quad1.quad.com> Date: 9 Dec 87 00:36:22 GMT References: <289@cresswell.quintus.UUCP> <6748@brl-smoke.ARPA> <290@cresswell.quintus.UUCP> Reply-To: oleg@quad1.quad.com (Oleg Kiselev) Organization: HASA Lines: 13 Keywords: errno fclose fopen stdio errors In article <290@cresswell.quintus.UUCP> ok@quintus.UUCP (Richard A. O'Keefe) writes: >Here at Quintus, ... [I] have to worry about 4.2, 4.3, V.2, V.3, VMS, and >SAS Lattice C for MVS and VM/CMS. The best solution would be to write your own portable libraries with your own error handling mechanisms. That's what was done here, at Quadratron. So far, this approach seems to be the best way to solve portability problems of complex software systems. -- Oleg Kiselev -- oleg@quad1.quad.com -- {...!psivax|seismo!gould}!quad1!oleg HASA, "A" Division DISCLAIMER: I don't speak for my employers.