On Thu, Sep 12, 2019 at 8:15 PM Ivan Baidakou <i.bayda...@crazypanda.ru> wrote:
> As this is generic issue on Windows-platform, I'm not so sure that this *is* a generic issue on Windows. Consider the modules Hash::Util and List::Util, both of which load their own separate Util.dll. If it were a generic issue, I would think that loading both of those modules would create the same sort of clash as you're seeing with your modules. But that doesn't happen: C:\_32>perl -MHash::Util="all_keys" -MList::Util="uniqnum" -le "print 'ok 1'" ok 1 C:\_32>perl -MList::Util="uniqnum" -MHash::Util="all_keys" -le "print 'ok 2'" ok 2 If you can show me how the issue can be reproduced using Hash::Util and List::Util, then I'll be in agreement that there's a generic Windows issue interfering here. Otherwise, I'll remain a little suspicious of the way that you're various *::XS modules are being loaded. (On reflection, you might argue that, even if you *are* loading the modules in an unusual way, it's still a *generic* Windows issue ;-) > I think it should be fixed in via enabling d_libname_unique. It would be nice to hear devs, why not enable this option. My guess is that this would be unfeasible on Windows (because the docs suggest that it's solely for the benefit of Android) ... but I am only *guessing* about that. Cheers, Rob
