At 10:59 AM 7/31/2001 +0100, Dave Mitchell wrote:
>Bart Lateur <[EMAIL PROTECTED]> wrote:
> > This came up on comp.lang.perl.misc once, and Ilya Z. then wrote, IIRC,
> > that there's no reason why the DLL (if I may call it this way) should
> > have a name identical to the module name. His example was that on his
> > port, for OS/2, he added a (machine generated) versioning string.
> >
> > I think this is a good time to generalise that practice.
>
>This will help with with DLL/.so's that are compiled from XS, but doesn't
>solve the problem of 3rd-party libraries.
Yup. We've had this issue for ages on VMS (though the effects are always
process-specific and we don't have leakage) and it's reasonably easy to
deal with on the perl level with appropriate module shareable image names.
As you say, though, there's no way to get around this for external
libraries that we link against if they don't do similar things.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
