Do I understand you correctly? You would have My:: namespace be like private and Our:: namespace be like protected

No :-)

My:: and Our:: 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.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.