From owner-freebsd-bugs  Thu Nov  6 18:20:05 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA01204
          for bugs-outgoing; Thu, 6 Nov 1997 18:20:05 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA01194;
          Thu, 6 Nov 1997 18:20:01 -0800 (PST)
          (envelope-from gnats)
Date: Thu, 6 Nov 1997 18:20:01 -0800 (PST)
Message-Id: <199711070220.SAA01194@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: fenner@parc.xerox.com, tege@nada.kth.se
Cc: FreeBSD-gnats-submit@freebsd.org, tege@pdc.kth.se
Subject: Re: bin/4961: Problems with fseek and fprints
Date: Thu, 6 Nov 1997 18:15:37 PST

 The ANSI C Standard, section 7.9.5.3, says:
 
 
 Opening a file with append mode ('a' as the first character in the mode
 argument) causes all subsequent writes to the file to be forced to the then
 current end-of-file, regardless of intervening calls to the fseek function.
 
 
 I don't know how to do what you want to do with ANSI C.
 
   Bill