Also the "my" was removed from the @ISA and @EXPORT global arrays

Oh, I missed in your original code that you used 'my' when it should have been 'our'. The 'our' keyword declares a global package variable1, where 'my' declares a lexical variable that can't be seen by Exporter afterward.

As Corion pointed out, you should put back strict and warnings (which will still work once you declare the variables with 'our'), and use Exporter 'import'; is cleaner than messing with our @ISA=('Exporter').


(1) Actually, 'our' adds a global package variable into your lexical scope, which is a little bit different from "declaring a global".

In reply to Re^3: Using Win32::SerialPort in a module by NERDVANA
in thread Using Win32::SerialPort in a module 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.