Re: 'what' doesn't use perror to print open errors, Sys V/3.0

Article View: comp.bugs.sys5

Article #1071

#1071

From: Ubben Greg
Date: Sun, 30 Apr 1989 02:11

12 lines
1045 bytes

In article <10156@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
> (1) "what" uses fopen() to open the file.  perror() is inappropriate
> except when a system call reports failure.  fopen() is not a system call.
> ...

I regularly use perror() to report the failure of an fopen().  It works on
all the systems I've used because, of course, the fopen() doesn't make any
other system calls after the open().  Is this really a bad thing to do?
confirm: 

					-- Greg Ubben
					   bink@aplcen.apl.jhu.edu

Technical Details

Message-ID: <1153@aplcen.apl.jhu.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!indri!aplcen!bink

References: <3759@sugar.hackercorp.com> <10156@smoke.BRL.MIL>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!indri!aplcen!bink
From: bink@aplcen.apl.jhu.edu (Ubben Greg)
Newsgroups: comp.bugs.sys5
Subject: Re: 'what' doesn't use perror to print open errors, Sys V/3.0
Summary: Should one REALLY not use perror with stdio?
Message-ID: <1153@aplcen.apl.jhu.edu>
Date: 30 Apr 89 02:11:55 GMT
References: <3759@sugar.hackercorp.com> <10156@smoke.BRL.MIL>
Reply-To: bink@aplcen.apl.jhu.edu (Greg Ubben)
Organization: The Johns Hopkins University, Baltimore MD
Lines: 12

Reply to Parent Message