Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.8 $; site uiucuxc
Path: utzoo!watmath!clyde!cbosgd!cbdkc1!desoto!packard!ihnp1!ihnp4!inuxc!pur-ee!uiucdcs!uiucuxc!hamilton
From: hamilton@uiucuxc.Uiuc.ARPA
Newsgroups: net.bugs.4bsd
Subject: Re: Bug in isatty (all systems!)
Message-ID: <2200013@uiucuxc>
Date: Sun, 4-Aug-85 16:58:00 EDT
Article-I.D.: uiucuxc.2200013
Posted: Sun Aug  4 16:58:00 1985
Date-Received: Tue, 6-Aug-85 10:27:45 EDT
References: <965@sdcsvax.UUCP>
Lines: 8
Nf-ID: #R:sdcsvax.UUCP:-96500:uiucuxc:2200013:000:409
Nf-From: uiucuxc.Uiuc.ARPA!hamilton    Aug  4 15:58:00 1985


> No where does the documentation explicitly say "Some routines which return
> successful results may, as a side-effect, set the value of errno to an
> arbitrary value."  In addition, I would consider such cases to warrant
> mention in the "Special Considerations" :-) section.

of course the documentation doesn't say that.  it isn't true.
isatty() and mktemp(), for example, don't even "know" errno exists.