Xref: utzoo comp.lang.c:40075 comp.unix.aix:5739
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!ut-emx!ibmchs!auschs!awdprime!awdprime.austin.ibm.com!dls
From: dls@achilleus.austin.ibm.com (David Skeen)
Newsgroups: comp.lang.c,comp.unix.aix
Subject: Re: when to fflush ?
Message-ID: <DLS.91Jun14130805@achilleus.austin.ibm.com>
Date: 14 Jun 91 17:08:05 GMT
References: <504@bally.Bally.COM>
Sender: news@awdprime.UUCP
Reply-To: David Skeen <dls@dce.austin.ibm.com>
Followup-To: comp.lang.c
Distribution: usa
Organization: IBM Austin (PSP)
Lines: 10
In-reply-to: siva@bally.Bally.COM's message of 13 Jun 91 15:51:36 GMT

The description of fseek() in the X/Open Portability Guide (issue 3)
says that "If the stream is writable and buffered data had not been
written to the underlying file, fseek() will cause the unwritten data
to be written to the file and mark the st_ctime and st_mtime fields of
the file for update."  I did a quick scan of POSIX 1003.1-1990, but
didn't find such an explicit statement.
--
Dave Skeen                     IBM Internal: dls@achilleus.austin.ibm.com
D61/803  Zip 2603              IBM VNET:     SKEEN at AUSTIN
Austin, TX 78758               Internet:     dls@dce.austin.ibm.com