Answer to C++ Programming Puzzle

The answer is there are at least four. The first one is quite subtle:

1. You can overwrite the private variable like this!
   *Earth.GetPlanetName() = 0;
That's not exactly private!
2. It doesn't trap a null name.
3. It leaks in two places! When the object goes out of scope, nothing frees up PlanetName. There's no destructor.
4. When a new name is assigned, the old one is lost but the memory is not freed up. Another leak!

C++ is probably one of the most annoying languages for having subtle bugs - but I suppose that's the price for all that programming power. They catch me out as well! Mind you if you think that's bad try templates!