JK> For example, is cin << somestring; safe? 
Yes, as long as the string is properly NUL-terminated.  It won't do much, 
however, since all output to an istream such as cin will cause an error.  
        
 JK> if an array has 3 elements (0-3) I cannot store "the" as there will
 JK> be no null character, 
If an array has 3 elements, they will be numbered 0 to 2, not 0 to 3.  
Otherwise, you are correct.
 ¯ JdeBP ®
--- FleetStreet 1.19 NR
 BP> struct base {
 BP>     int f();
 BP>     int f(int,int);
 BP> } ;
 BP> struct derived : public base {
 BP>     int f();
 BP> };
 BP> derived a ;
 BP> a.f(1,2) ;                // ERROR
 BP> [Redefining] f() and inheriting parent's f(int,int) without 
 BP> additional problems would be [more] intuitive, and make no more 
 BP> work to the compiler.
Yes it would.  It would complicate name lookup enormously, since it would 
have to perform overload resolution across multiple scopes simultaneously.  
As the current language rules stand, name lookup occurs first, finding the 
`f' in the scope of class derived, and *then* overload resolution occurs, in 
the scope of the name that is found.
 ¯ JdeBP ®
--- FleetStreet 1.19 NR
---------------