Nothing really wrong with your script so I'll nitpick

    next if /^(\s)*$/;  # skip blank lines
    my($Temp)=$_; #Store each line from $FileName to $Temp
    chomp ($Temp); #strip eol character
    push @fileExtArr, $Temp;

[download]

The parens around \s are unnecessary. $Temp is unnecessary, just continue to use $_

# go to this key for value
...
# check this key for these values

[download]

Bad comments. I like comments, but they have to give more information than what you can as easily read from the code itself. If words like 'this' and 'these' show up frequently, the comments likely are wasted time.

In reply to Re: tieregistry file ext search script critique by jethro
in thread tieregistry file ext search script critique by gebuh

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.