Date:	Mon, 07 May 2001 21:10:51 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp-workers AT delorie DOT com
Message-Id:	<3405-Mon07May2001211050+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC:	libstdc++@gcc.gnu.org, pavenis AT lanet DOT lv
In-reply-to:	<3AF6FB4E.3915.208439A@localhost> (pavenis@lanet.lv)
Subject:	Re: libstdc++-v3: bug in handling text files for DJGPP
References:	<3AF6FB4E DOT 3915 DOT 208439A AT localhost>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: pavenis AT lanet DOT lv
> Date: Mon, 7 May 2001 19:45:18 +0300
> 
> basic_filebuf::sync() always advances file pointer by number of bytes 
> stored in buffer for output (see seekoff at end of this procedure).
> 
> It's OK for example for Linux when there is no special format for text 
> files. For DOS (and perhaps also Windows) we're getting problems as 
> adding CR before LF is done by fwrite() and as result sync() 
> incorrectly moves current pointer back.

DO I understand correctly that libstdc++ uses its own buffering (as
opposed to the buffering code implemented in libc.a for stdio)?

If so, it should use code similar to what the DJGPP library does for
buffered I/O functions.

- Raw text -