Thanks everyone for your responses. I've heard a range of possible solutions to address the issue, each with their own merits. I agree with merlyn that using full OO for this small module might be overkill. Some of the other solutions don't allow for two levels of defaults, one of the features I like about my current implementation.

So what I've done is to document the code a bit as it is and release that publically. I'm still interested in further feedback on how to best make this work-- I'm hoping that by publishing the code and documentation the issue will become more clear.

http://summersault.com/software/cascade/cgi_err/

Any feedback is appreciated. Thanks!

-mark

---

---

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, 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, 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.