[npoc]

Just because it's newer doesn't make it better. There are good reasons for avoiding iostream

[tsimionescu]

That's my point - iostream is a really bad piece of code, and if you're anyway going to use modern C++, it's really recommended to stop using it.

[npoc]

Sorry, I got your comment completely backwards

[pjmlp]

iostream is good enough for most jobs, unless one is writing high performace IO code battling for each ms.

[tsimionescu]

Or unless one wants to write formatted output, or unless one wants to handle IO errors with RAII...

[pjmlp]

Perfectly fine with existing operators and handle classes.

Happily using iostreams since Turbo C++ 1.0 for MS-DOS in 1993, and will keep doing so, unless chasing ms optimizations.

[spacechild1]

> There are good reasons for avoiding iostream

I guess that's not what you wanted to say, but I fully agree :)