$VERSION, @ISA, @EXPORT, etc. must all be package variables. You have declared them as lexical variables instead, which means that as far as Exporter et al. are concerned, they don't exist. (In fact, since they're lexicalized to the BEGIN block, they don't exist for the rest of your module either.) This is why all the examples show use vars qw/@EXPORT @EXPORT_OK .../; instead.

Note also that you want to import qw(IPGrab), rather than qw(:IPGrab), because you don't have an :IPGrab export tag.

In reply to Re: Win32 EXPORT_OK problems by chipmunk
in thread Win32 EXPORT_OK problems by InfiniteSilence

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.