I came across the following \"strange\" feature today - if you have a reference to an object from the class A in the body of the class A you can access the private fields of
Those keywords are class-oriented, not object-oriented. So it just looks and sees "oh huh, an object of class Foo is trying to access a private object on Foo. Well, that's fine".