Depending on what the real code looks like I would probably be pretty pissed to inherit it. It seems like the code layout is fairly arbitrary. And while you will find some range of opinions on the topic, code comments are an extremely poor substitute for Pod and history files and I only welcome comments where they are brief and clarify business logic decisions or explain why a sub-optimal choice is necessary (dependencies, side-effect, legacy support) and not just bad code.

moritz has probably given the best idea from what I can understand of the problem. Roles (via Moose) would allow (and really steer) better categorization/separation of parts of your code while making its end use more intuitive. Moose is not easy to dive into but it's really cool once you do and the community is supportive.

---

---

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.