in reply to Re: ActiveState modules
in thread ActiveState modules

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\

Replies are listed 'Best First'.
Re^3: ActiveState modules
by BrowserUk (Patriarch) on Mar 03, 2005 at 12:38 UTC

    A good point worth noting++

    As it is, I still use the older version of VC++ (Microsoft (R) 32-bit C/C++ Standard Compiler Version 13.00.9466 for 80x86) for anything Perl related, but I'm not sure if this is still available for download anywhere?


    Examine what is said, not who speaks.
    Silence betokens consent.
    Love the truth but pardon error.