I'll check that out. I've gotten in the habit of using variable caching for methods I might repeatably call (ie, db method to return the db object) and use did basic isset() checks; setting the value if false and returning the variable.

That can be useful for methods were I have a rather large return array and want to free up some memory instead of keeping the values stored in a local variable (pretty much what I'm needing and more). Thanks!

And the module part, generally this is true although some stronger modules (especially ones that start playing around with memory and system level stuff) requires compiled code. So I just wanted to make sure I cleared that restriction before I get a slew of mem_cache type modules suggested

---

---

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.