my %names = ();

is better as:

my %names;

Hashes and arrays are made fresh (and empty) when they are declared so you don't need to clutter code with redundant initialization.

Avoid nested blocks. Your for loop is better written:

for my $name (sort keys %names) {
    # Skip if fewer than 4 occurrences of name or none over 50
    next if @{$names{$name}} < 4 || !any {$_ > 50} @{$names{$name}};

    say "$name: ", join ",", @{$names{$name}};
}

[download]

Use early exits to avoid nesting in loops and subs. Nested blocks makes logic flow much harder to analyze. Using early exits allows a simple to understand list of test/handle/bail steps.

Premature optimization is the root of all job security

In reply to Re^2: Filtering text file made into hash by GrandFather
in thread Filtering text file made into hash by reebee3

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.