The problem with malloc and free: they don’t know about constructors and destructors

Advantage of iostream: type safety

iostream vs iostream.h: isostream has its own namespace.

Summary:

Virtual functions must be members. If f needs to be virtual, make it a member function of C.

operator>> and operator<< are never members. If f is operator» or operator«, make f a non-member function. If, in addition, f needs access to non-public members of C, make f a friend of C.

Only non-member functions get type conversions on their left-most argument. If f needs type conversions on its left-most argument, make f a non-member function. If, in addition, f needs access to non-public members of C, make f a friend of C.

Everything else should be a member function. If none of the other cases apply, make f a member function of C.

Classic example of why sometimes macro is a bad idea:

The explicit keyword in C++ is used to declare explicit constructors. Explicit constructors are constructors that cannot take part in an implicit conversion