I would move all the calls to $cgi->param outside of the wanted sub. That is executed for every file being iterated on; probably not what you want to do.

Also, the only thing you're doing is checking if the CGI parameters are set, you're not doing anything with the files being iterated on. If you want to search for a string in the contents of each file, you'll have to open each file, then iterate on the file contents. Of course you'll want to do this only once per file, using open.

If I were doing it, I would probably construct a big regex based on the selected search options, and check for a match of that regex as I iterated on each file's contents. But you have some flexibility here. Maybe with a more specific question we can be of more use?


In reply to Re: Questions on File::Find by revdiablo
in thread Questions on File::Find by hok_si_la

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &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.