Technically, the following is incorrect:

#Now declare what we permit to be visible within the module.

Putting things in @EXPORT or @EXPORT_OK doesn't mean that those elements are 'visible', it means that they can be imported by the user of the library. @EXPORT means that those subroutines are imported by the calling script automatically when they use your module, and @EXPORT_OK means the caller has to import them explicitly. It is always advisable to allow a caller to choose what they want to import (ie. best always to use @EXPORT_OK).

Also, here:

our @EXPORT = qw( &Serial_Init &Serial_TrxRcv &Serial_Close);

... you don't need the ampersands (ie. '&').

In reply to Re: Win32::SerialPort, buffer overflow by stevieb
in thread Win32::SerialPort, buffer overflow by jmClifford

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.