It's kinda hard to check your code without some data to drive match_query. However if $count doesn't get any entries the assignment my $max_count = shift @array; will assign undef and give the warning described.

Note that your code is very Cish making it harder than it needs to be to see what is going on. Replace your C for loops with Perl for loops over the range 0 .. length($key)-1 for a start. You should also use %count and %element so it's obvious what type is being used instead of depending on some Perl magic to create an appropriate reference at run time. That makes the code easier to read and provides better error checking.

Don't use prototype subs (sub match_query() {). They don't do what you want and in the case of match_query your prototype is clearly wrong. The sub says don't give me any arguments in the prototype, then shifts off two arguments!

If the hint in the first paragraph isn't enough you'll need to mock up something to call match_query with appropriate arguments that we can run ourselves.

Premature optimization is the root of all job security

In reply to Re: Help with function, count matches and store in hash & retrieve sorted by GrandFather
in thread Help with function, count matches and store in hash & retrieve sorted by Pathogenomix

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.