From owner-freebsd-bugs  Fri Nov  7 10:40:03 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA15456
          for bugs-outgoing; Fri, 7 Nov 1997 10:40:03 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA15436;
          Fri, 7 Nov 1997 10:40:01 -0800 (PST)
          (envelope-from gnats)
Date: Fri, 7 Nov 1997 10:40:01 -0800 (PST)
Message-Id: <199711071840.KAA15436@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bill Fenner <fenner@parc.xerox.com>
Subject: Re: bin/4961: Problems with fseek and fprints 
Reply-To: Bill Fenner <fenner@parc.xerox.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/4961; it has been noted by GNATS.

From: Bill Fenner <fenner@parc.xerox.com>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: bin/4961: Problems with fseek and fprints 
Date: Fri, 7 Nov 1997 10:33:24 PST

 Garrett Wollman <wollman@khavrinen.lcs.mit.edu> wrote:
 >Unless an error is indicated, the value of errno is indeterminate.
 
 That's what I always thought, too.  Footnote #93 of the ANSI C standard says:
 
 ... a program that uses errno for error checking should set it to
 zero before a library function call, then inspect it before a subsequent
 library function call.
 
 However, the ANSI C standard also says
 
 The value of errno may be set to nonzero by a library function call
 whether or not there is an error...
 
 so it seems to be inconsistent with itself.  Oh well.
 
   Bill