Safer is always slower. You have the same issue in other languages like Java, where internal methods could access properties directly or call other methods.

That issue is neither here nor there. You had to run 10 million method accesses to get an amount of time that was reasonable to measure. That's not a performance problem. My rule of thumb is that classes are allowed to access properties directly within their own class only. An inheriting class should use accessors.

The real problem that you're stumbling on here is that it's basically not possible to inherit from a class in Perl without understanding the data structures of the class you're inheriting from, at least enough to avoid stepping on them. That is an annoyance, but hasn't kept me from using OO in Perl. I rarely use inheritance, and when I do it is usually between two classes that I know well.

---

---

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.