Change of behaviour, or something broke in cin/streambuf behaviour between 3.3.4 and 3.4.1?

[Andrew Walrond]

On Wednesday 22 Sep 2004 10:59, Paolo Carlini wrote:
>
> In my opinion, the current behavior is correct. Indeed, something changed
> but didn't 'break' ;) (*) Basically, the reason is that in 3.4.x we have
> a new
> unbuffered filebuf for cin, cout & co, which *improves* considerably the
> correctness of the library in its interactions with stdio. This streambuf
> is used, correctly, by default.

Thanks Paulo (for the lightning fast response+explanation).

I'll go fix my applications :)

Andrew Walrond