No. Next question.

Seriously, CGI.pm is a terrible example of interface design. The OO interface is constantly breaking because of the need to support the non-OO one, which relies on lots of globals and requires crazy stunts in long-running environments like mod_perl and FastCGI.

Here are some reasons to avoid mxing:

• Inevitably means more code to maintain, test, and change. Your code would require changes in multiple places if you modify the parameters a function takes.
• Ruins OO features like inheritance.
• You didn't actually do this in your example, but having some subs that are called as functions and some that are called as class methods in the same package inevitably leads to confusion and bugs caused by mistakenly calling one the wrong way.

---

---

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.