> Well, if I use libraries to avoid C's pitfalls, that language will be safe, too.

I'm not talking about possibilities, but about libraries that are actually available and widely used.

> You might as well say the key to using C++ is to use Python or C instead.

And that might not be a bad idea. If you don't need the power of C++ or don't want to invest time in learning it, then you are better off using a simpler language such as Python, but probably not C for the reasons I pointed out earlier.

C++ is a complicated language, so I agree with your advice of using good learning resources and code review. I don't agree that the issues you mentioned are of the same level as the ones I was talking about. Missing a copy constructor is just not as big of a problem as, say, getting a segfault caused by misuse of varargs.