Article View: comp.bugs.sys5
Article #1069Re: 'what' doesn't use perror to print open errors, Sys V/3.0
From: Doug Gwyn
Date: Sat, 29 Apr 1989 01:53
Date: Sat, 29 Apr 1989 01:53
9 lines
929 bytes
929 bytes
In article <3759@sugar.hackercorp.com> karl@sugar.hackercorp.com (Karl Lehenbauer) writes: >Several years have elapsed, which should have been long enough to make all >the programs distributed with Unix follow the perror() conventions that >the manuals tell us our programs are to follow. (1) "what" uses fopen() to open the file. perror() is inappropriate except when a system call reports failure. fopen() is not a system call. (2) SCCS was developed long ago and hasn't been modernized.
Technical Details
Message-ID:
<10156@smoke.BRL.MIL>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!adm!smoke!gwynReferences:
<3759@sugar.hackercorp.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn) Newsgroups: comp.bugs.sys5 Subject: Re: 'what' doesn't use perror to print open errors, Sys V/3.0 Message-ID: <10156@smoke.BRL.MIL> Date: 29 Apr 89 01:53:47 GMT References: <3759@sugar.hackercorp.com> Reply-To: gwyn@brl.arpa (Doug Gwyn) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 9