We see here that behind the scenes there are really two name fields of a Child object. The private scoping on the variable seems to go one step further than in other languages and actually scope the private variable to only the class declaring it, not simply disallowing access to children.

This is kind of cool in the sense that you don’t have to worry about your parent classes’ variable names but, as shown above, can also be quite confusing.

Thanks for commenting!

Technically you are not overriding anything, because the name variable (in my mind) doesn’t exist in the child if it’s set to private in the parent. However if you use protected and do not specify that you’d like to override with the override keyword, then you’ll probably get an error.