Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!caen!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!ncoast!dale
From: dale@NCoast.ORG (Dale Smith)
Newsgroups: comp.lang.c++
Subject: Re: Large stream buffers
Message-ID: <1991Jun19.132733.3882@NCoast.ORG>
Date: 19 Jun 91 13:27:33 GMT
References: <1991Jun17.171623.6730@NCoast.ORG> <772@taumet.com>
Organization: North Coast Public Access Un*x (ncoast)
Lines: 18

In article <772@taumet.com> steve@taumet.com (Stephen Clamage) writes:
>dale@NCoast.ORG (Dale Smith) (me) writes:
>
>>How can I prevent an ofstream from flushing it's buffer until it's
>>full?  In Borland C++, if I allocate a larger buffer (say 32k or so),
>>I still seem to be doing a lot more writes to disk than necessary.
>
>Check the buffering flags ios::stdio and ios::unitbuf for the various
>output streams.

These bits are not set, at least as far as I can tell with TD.  In the
header files, they are never set, only checked.  ??????

dale
-- 
 Dale P. Smith
 dale@ncoast.org                         dale@harco3.uucp
 uunet!usenet.ins.cwru.edu!ncoast!dale   uunet!aablue!fmsystm!harco3!dale