In your place, I wouldn't make it three subs. I'd make it just one sub, with a mode parameter indicating how you want it searched. Like this:
search(simple => $stuff);
search(normal => $stuff);
search(extended => $stuff);
The definition of the
search routine then could look like this:
use Carp;
sub search($$) {
my(%parameter); # Those parameters that you set
my $mode = shift;
if($mode eq 'simple') {
# set parameters to simple
...
} elsif($mode eq 'normal') {
# set parameters to normal
...
} elsif($mode eq 'extended') {
# set parameters to extended
...
} else {
croak("mode '$mode' not supported");
}
# Now just do your process_search
...
}
And your problem simply evaporates.
Any former syntax related problems, i.e. use of an invalid mode, would now only be detected at runtime, thus when the call is made. But actually that's not different from the original code, where a call to an undefined sub would only be detected when an attempt to call it, is made.
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.