Here's another problem:

... $findit .= "/\Q$term\E/i $param ";
[download]

It appears that you want the match to be case insensitive when matching $term. The way to specify that is as follows:

$findit_re = "\\b(?i:\Q$term\E)\\b";
[download]

This turns on case-insensitive matching for $term. Also, note the use of double-slashes since double quotes are being used. An easier way to write this is to use qr//:

$findit_re = qr/\b(?i:\Q$term\E)\b/;
[download]

At first I thought you were confused about the use of \Q...\E. After more carefully reading your response I don't think this is the case, but here is what I wrote about it:

\Q and \E is simply another way of invoking the the quotemeta() function - it just escapes characters which are used to denote regular expression elements.

For instance, suppose you wanted to search for the three character sequence [a], i.e. a left bracket, the letter 'a', and then a right bracket, If you used the regular expression:

my $target = "[a]";
if ($string =~ m/$target/) { ... }
[download]

it wouldn't work as you wanted because the brackets would be be interpreted as being part of the character class regex element. You can fix things by using quotemeta or \Q...\E as follows:

my $target = "[a]";
if ($string =~ m/\Q$target\E/) { ... }
# or:
my $re = quotemeta($target);
if ($string =~ m/$re/) { ... }
[download]

Now you'll only get a match if $string contains the three character sequence [a].

Another way to think about it is that the quotemeta is a function which converts a string to a regular expression which matches exactly that literal string.

---

---

• 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.