First, I'd use more than one space for indentation. I use 4 because I like the way it discourages overly deep nesting of code. Even 2 or 3 would be quite a bit better than 1, IMO.

$Traps{"$Fields[6]"} = [ $Expiration,$Fields[2],$Fields[5],$Fields[7] ]; can be written $Traps{$Fields[6]} = [ $Expiration, @Fields[­2,5,7] ]; Putting in too many quotes can bite you (though using it as a hash key also does the stringification which would bite you in the same way in this case -- changing an object into a string) so be careful of it.

You can make the code clearer using a few constants: 

    sub EXPIRE() { 0 }
    sub WHATEVER() { 1 }
    sub FOOBAR() { 2 }
    sub FILENAME() { 3 }

[download]
(these make no difference in the running time of the code since they get optimized away at compile time). I'd also avoid 'unless' so push @GrepList,$Traps{$tr­ap}[3] unless (($Traps{$trap}[0] < $Now && $Traps{$trap}[1]) || $trap eq "SIZE"); becomes 
push @GrepList, $Traps{$tr­ap}[FILENAME]
    if  $trap ne "SIZE"
   and     ! $Traps{$trap}[WHATEVER]
        || $Now <= $Traps{$trap}[EXPIRES];

[download]
for example (I find spacing more effective at conveying grouping than parens, YMMV).

Don't use map unless you want the list that it builds: map { $MaxLen = length($_) if length($_) > $MaxLen } @GrepList; becomes 

for(  @GrepList  ) {
    $MaxLen = length($_) if length($_) > $MaxLen;
}

[download]
If you really have a need for single-line code (which is a mistake in my book), then remove the newlines.

Use local( $/ )= \$BufferSize; and you can drop the $/ = "\n"; line.

So no speed improvements to offer. (:

                - tye

In reply to Re^3: Shell Script Woes (review) by tye
in thread Shell Script Woes by Limbic~Region

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.