4 ms·
Just because it's newer doesn't make it better. There are good reasons for avoiding iostream
by npoc 2y ago
Just because it's newer doesn't make it better. There are good reasons for avoiding iostream
- tsimionescu 2y agoThat'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 2y agoSorry, I got your comment completely backwards
- pjmlp 2y agoiostream is good enough for most jobs, unless one is writing high performace IO code battling for each ms.
- tsimionescu 2y agoOr unless one wants to write formatted output, or unless one wants to handle IO errors with RAII...
- pjmlp 2y agoPerfectly 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 2y ago> There are good reasons for avoiding iostream I guess that's not what you wanted to say, but I fully agree :)