If you want to create a package global variable that is private, you should use 'my', not 'our', as 'our' will expose the variable to external tampering. Really, though, I'm not particularly fond of your idiom of setting global parameters that effect the behavior of other subroutines. This creates a level of indirection that will make debugging more difficult. I would instead favor an idiom of having your process_search subroutine take multiple arguments, having each of your specific search functions pass along the search that was handed to them, as well as pass along some parameters the control the behavior of your general process_search function. This makes your program behavior more functional, eliminating confusing and unnecesary state information from the class.

---

---

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.