A general maxim in programming is don't repeat yourself (usually abbreviated to DRY). I find this particularly relevant in Perl.

Blazar has already commented on your use of unnecessary C-style for loops and a clumsy, long sequence of elsif's.

You can replace

for ($count = 0; $count<=$#Comment; $count++)
{
    #clumsy, long sequence of elsif's
}

[download]

with

my @fields = qw/ Sensor Signal_level AUL ALL Recipe
                 Wafer_slot Step_Value /;

die "I did not expect " . @Comment . " columns!"
    unless @fields == @Comment;

for my $value ( @Comment )
{
    print shift @fields, " = $value\n";
}

[download]

In reply to Re: Parsing Script by FunkyMonk
in thread Parsing Script by phimtau123

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.