It should be noted that there are some caveats when compiling extensions with a different version of the compiler than that which compiled the Perl (which is the case when building modules for ActivePerl with the Visual C++ Toolkit), this is due to the fact that the C runtime libraries will reside in different DLLs so OS level objects that might be shared between Perl and the extension that are defined in the runtime (such as HANDLEs and so forth) will not be valid in the part that didn't define them. I was recently caught out by this with respect to Term::ReadKey and it is discussed here

Of course modules that don't share C runtime thingies with Perl shouldn't be affected by this.

/J\

In reply to Re^2: ActiveState modules by gellyfish
in thread ActiveState modules by thekestrel

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.