This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/10063] [3.4 Regression] stdio_filebuf broken


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10063



------- Additional Comments From peturr02 at ru dot is  2003-07-01 09:48 -------
Paolo Carlini wrote:
> Personally, I don't know what should we really do in order to be able to
> intermix flawlessly the current stdio_filebuf - which, at variance with the old
> situation ends up always issuing direct non blocking I/O syscalls, i.e., read,
> write, lseek and so on - with stdio.

Since this class doesn't use stdio any more, it should be named something other
than stdio_filebuf.

> Perhaps we should just hit the bullet and
> declare that this is now possible only with stdio_sync_filebuf?

Sounds good. stdio_filebuf was never really well suited for this purpose.

Petur


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]