use Test::More;

You are deliberating over what tool to use, but I would invite you to postpone that question and get busy writing a test suite.

What do you want your class to do? Have your test suite cover every interface method (including the constructor and the accessors), but above all convince yourself that a class that passes your tests will accomplish your goals.

I confess I find it hard to write tests when I really want to be coding the implementation, but I remind myself that

• tests are code too, and I enjoy writing them once I get started;
• coding the implementation is way more fun when I have a test suite in hand;
• managers asking after specs and documentation have been known to accept a well-commented test suite, or failing that, the test suite is a good outline for a requirements document.

Now you can safely pick a tool at random from among your favorite answers in this thread. You can even change your mind later and convert your classes to a different implementation. If your design is properly encapsulated, you'll be fine.

That said, I do have my own preference for inside-out or flyweight implementations. I think building classes in this way is like use strict. It catches dangerous practices (in this case, accessing your object's internals directly) at an earlier stage of development.

---

---

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.