delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2004/10/21/18:00:26

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: fstream and fflush
Date: 21 Oct 2004 21:54:30 GMT
Lines: 14
Message-ID: <2tqpgmF245sdvU4@uni-berlin.de>
References: <cl92jr$3ro$1 AT coranto DOT ucs DOT mun DOT ca> <cl96k3$45r$1 AT coranto DOT ucs DOT mun DOT ca>
X-Trace: news.uni-berlin.de wlHhkEgTE73ipWdRzfYX5Q55Q7gpRgjZRPmpjcusfC6g1GXkyix6x4yUbT
X-Orig-Path: not-for-mail
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Jason Mills <jmills AT cs DOT mun DOT ca> wrote:

> After more tests, I discovered that fstream::flush() and
> fflush(NULL) both will not flush the stream if I am writing rapidly
> to the stream.  If I sleep(), (maybe if I a do other work, I have
> not checked) the stream is eventually flushed. Can someone explain?

What exactly do you expect flush() to do for you, if you keep writing
stuff to the file afterward, i.e. how do you define that it did "not
flush the stream"?

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019