Nice goodie, but I've three comments:

1. Why having two arrayrefs dealing with the same information, i.e. methods? This seems error-prone from a user (= programmer)'s point of view. Wouldn't a hashref with names as keys and coderefs as values be more transparent?
2. As a second remark: you can define objects, but it would be convenient to have the concept of classes since with this approach types seem rather ad hoc. Two objects of the same class need not have the same methods, which is sometimes convenient but... ehrm, unpleasant in general
3. I'm not very fond of the $obj->incant('action', @args) invocation, but granted, that's personal taste (or lack thereof ;-) The incant seems to diminish readability.

Just my 2 cents, -gjb-

---

---

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.