Do I understand you correctly? You would have My:: namespace be like private and Our:: namespace be like protected
were two alternate names for the same code. On reflection I decided that My::
was probably a poor choice since my
is all about scoping lexical variables, while our
is about scoping the name of package variables which, from a certain somewhat skewed perspective, is what I'm doing in the code.
Calling the functionality "private" or "protected" is potentially confusing since it doesn't do all the things that "private" and "protected" do. All it does is allow you to conveniently name a package for implementation methods so you can avoid having them interfere with your classes published interface.