Why should I use <iostream> instead of the traditional <cstdio>?, C++ FAQ

C++ FAQ / Section 15 / FAQ 15.1

Section 15:

15.1	Advantages of `<iostream>` over `<cstdio>`?
15.2	Understanding infinite loop when the input is invalid?
15.3	How can I get `std::cin` to skip invalid input characters?
15.4	How does that funky `while (std::cin >> foo)` syntax work?
15.5	Why does my input seem to process past the end of file?
15.6	Why is my program ignoring my input request after the first iteration?
15.7	Should I end my output lines with `std::endl` or `'\n'`?
15.8	How can I provide printing for my `class` `Fred`?
15.9	Using a `printOn()` method vs. a `friend` function?
15.10	How can I provide input for my `class` `Fred`?
15.11	Providing printing for an entire hierarchy of classes?
15.12	How can I open a stream in binary mode?
15.13	"Reopening" `std::cin` and `std::cout` in binary mode?
15.14	How can I write/read objects of my class to/from a data file?
15.15	Sending objects over a network?
15.16	Backslashes in filenames?
15.17	How to capture key presses before the ENTER key?
15.18	How to turn off screen echo on keyboard input?
15.19	How can I move the cursor around on the screen?
15.20	How can I clear the screen?
15.21	How can I change the colors on the screen?
15.22	How can I print the numeric value of a `char` or `char*`? Updated!

[15.1] Why should I use <iostream> instead of the traditional <cstdio>?

Increase type safety, reduce errors, allow extensibility, and provide inheritability.

printf() is arguably not broken, and scanf() is perhaps livable despite being error prone, however both are limited with respect to what C++ I/O can do. C++ I/O (using << and >>) is, relative to C (using printf() and scanf()):

More type-safe: With <iostream>, the type of object being I/O'd is known statically by the compiler. In contrast, <cstdio> uses "%" fields to figure out the types dynamically.
Less error prone: With <iostream>, there are no redundant "%" tokens that have to be consistent with the actual objects being I/O'd. Removing redundancy removes a class of errors.
Extensible: The C++ <iostream> mechanism allows new user-defined types to be I/O'd without breaking existing code. Imagine the chaos if everyone was simultaneously adding new incompatible "%" fields to printf() and scanf()?!
Inheritable: The C++ <iostream> mechanism is built from real classes such as std::ostream and std::istream. Unlike <cstdio>'s FILE*, these are real classes and hence inheritable. This means you can have other user-defined things that look and act like streams, yet that do whatever strange and wonderful things you want. You automatically get to use the zillions of lines of I/O code written by users you don't even know, and they don't need to know about your "extended stream" class.