I got the following error message when run a Perl script.

Prototype mismatch: sub main::INFINITE: none vs () at C:........../lib/Exporter.pm line 66.

at C:........app.pl line 40.

.

The lines near line 66 of Exporter.pm are (line is at the beginning of each line)

64 sub {require Carp; &Carp::carp} if not $SIG{__WARN__};

65 # shortcut for the common case of no type character

66 *{"$callpkg\::$_"} = \&{"$pkg\::$_"} foreach @_;.

67}.

.

The lines near line 40 of the app are.

38 use File::Basename;

39

40 use Win32::ChangeNotify;

I use the change notify function with the follwoing

$notify = Win32::ChangeNotify->new($watched_dir, 0, FILE_NOTIFY_CHANGE
+_SIZE);

[download]
Can someone kindly let me know how to remove the error?

This error seems to be ingored and Perl continues without any problems but I would rather not have it appear.

In reply to Puzzling Prototype Mismatch Error by merrymonk

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.