ack! why use chop when you can use the safer chomp? And how come neither was used inside the while (<MAPFILE>)? Finally, why did you remove the call to lc?

# chomp the inputs to remove the trailing \n
chomp(my $l = <STDIN>);

.
.
.

# 3-arg open safer.
# No use putting quotes around $sdtfile.
open(MAPFILE, '<', $sdtfile)
or die("Unable to open map file: $!\n");

# No need to load whole file in memory.
# Use while instead of foreach.
while (<MAPFILE>) {
   my (
      $date,
      $time,
      $lot,
      $waf,
      $ts,
      $sstep,
      $machine,
      $prog,
      $product,
      $plnfile,
      $striping,
   ) = map lc, split(/,/, $_);

   if (...) {
      .
      .
      .
   }
}

[download]

In reply to Re^2: parsing data from file by ikegami
in thread parsing data from file by Sunnmann

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.