Implementing Google or AltaVista in Perl for this kind of application is likely overkill, so here's a simple solution.

my (@names) = ( ... );

sub search
{
        my (@search_keywords) = split (/\s+/, shift);

        my ($match_code) = "sub{".join('&&', map { "/\Q$_\E/" } @searc
+h_keywords)."}";

        my ($match_func) = eval $match_code;

        return grep { &$match_func() } (@names);
}

my (@results) = search ("the fried potato king");
[download]

This will return all records that match all terms. For a version that matches any, switch the '&&' in the join() to be '||' instead.

Essentially, this 'search' function generates a subroutine that tells grep() if the array entry matches or not. You can have a look at the value of $match_code to see what it is doing.

The \Q and \E are used to escape the metacharacters which would interfere with the // regexp. Saves you from having to tr/// them yourself.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.