in reply to Re: Prototype mismatch error - ChangeNotify
in thread Prototype mismatch error - ChangeNotify

By carrying out your suggested test, I identified the two modules as process.pm and changenotify.pm.
I looked in both modules and could see both had INFINITE in the EXPORT. However, I could not recognize where either defined what INFINITE meant.
Therefore I suspect that there is some incompatibility between these two.
You also said “If the other place that imports it doesn't have a way to prevent it too, then a work-around
would be to use it inside a dummy package. It is only used in one line, so delegate that line to a function in that inner package, which you call from the main code.”
Although I have just Perl for some years it would help if you could give some more details.
I guess I should know(!) but I simply do not understand what you mean particularly with the ‘so delegate’ part of it.
  • Comment on Re^2: Prototype mismatch error - ChangeNotify

Replies are listed 'Best First'.
Re^3: Prototype mismatch error - ChangeNotify
by merrymonk (Hermit) on May 23, 2011 at 08:41 UTC
    I have had a very helpful reply from Christopher J. Madsen via RT bug-Win32-IPC@rt.cpan.org who suggested that in my case I can remove the problem by using
    use Win32::ChangeNotify qw(FILE_NOTIFY_CHANGE_SIZE);
    As this will just export _NOTIFY_CHANGE_SIZE from the module. Therefore there will not be any conflict with INFINITE. This worked so I no longer have a problem!
    Thanks for your help in pointing me in the right direction
      Ah yes, I should have thought of that. Listing the one thing you do want (or can tolerate) is different from using an empty () which will not call import at all (which is what I worried about).
Re^3: Prototype mismatch error - ChangeNotify
by John M. Dlugosz (Monsignor) on May 23, 2011 at 17:27 UTC
    # this is the main file $x= Helper::foo(); # ... package Helper; use PoisonModule qw/ bar INFINITE/; sub foo { return bar (blah, blah, INFINITE); }