PATCH for libstdc++/2211 (some discussion held on gcc-bugs)
Theodore Papadopoulo
Theodore.Papadopoulo@sophia.inria.fr
Tue Jul 3 11:51:00 GMT 2001
Hi Loren,
Sorry for not having replied. For some reason, I just did not seen
some of your E-mails. As far as I can tell, I agree with your
analysis about the fact that synchronisation does not necessarily
mean that the internal buffers should be of length 1. However, I do
not master of the arcane of the C++ standard to be sure to know all
the whereabouts (is this the correct word ?) of such a decision. I
planned to have a close look at the standard, but did not have time
up to now...
Anyway, I'll try your patch (with the example and also with more
complex code) and I'll tell you the results.
One point I can add is that when I reported the problem, I
hacked the libstdc++ files so as to not force the buffer for cin to
be of size 1 (there is such a line like this somewhere). Everything
worked fine. The compiler was used by maybe 5 or 10 people and no one
reported a problem. But I'm not sure anyone was mixing C and C++ IOs...
Thank's a lot for looking at this problem.
Theo.
--------------------------------------------------------------------
Theodore Papadopoulo
Email: Theodore.Papadopoulo@sophia.inria.fr Tel: (33) 04 92 38 76 01
--------------------------------------------------------------------
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.2 06/23/2000
iD8DBQE7QhQSIzTj8qrxOU4RAtFUAJ9JcDaQ1ffA7fA8cWwX91lr4YS2QwCfdSKH
W6Un7U7VKHF0Ib3G5ov2RYk=
=QDJd
-----END PGP SIGNATURE-----
More information about the Libstdc++
mailing list