As anonymonk puts it, "loop":
while( $run ) { my $newline = $objPort->lookfor; if ( $newline ne '' ) { print $newline; $run = 0 if $newline =~ /reason to stop/; } }

Another possibility is that your are_match() settings are matching "\n" and leaving "\r" on your lines, so when then print to the terminal, each line of text is overwritten. Try directing the output to file. That should show you if this is happening.

Also, be careful with "\n", because it can mean "\r\n" in some windows perl environments. You should consider using the hexadecimal escapes "\x0A" and "\x0D", as no magic happens with them.

Update: Fixed escape sequences. Thanks to BrowserUk.


TGI says moo


In reply to Re: Need help with Win32::SerialPort by TGI
in thread Need help with Win32::SerialPort by GoTerpsGo

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.