First: have you looked at the line indicated? Is it calling the indicated function correctly, or was there a braino when it was written?

Second: is the line indicated doing what you want it to do? Are you sure? Completely? Do you have a test that proves it is doing what you wanted?

If you are 100% sure that the call is correct as it stands, add a leading ampersand to the call to the subroutine to tell Perl to ignore the prototype: 

# Prototype mismatch was occurring here:
&index::encode(...);

[download]
Do not just do this to "make it go away". You may have a real problem (in fact, you almost certainly do!). Be sure you don't before you change anything.

Seriously. I considered whether or not to tell you this because I'm not sure you're going to do the legwork to ensure it's OK.

In reply to Re: Prototype mismatch using mod_perl by pemungkah
in thread Prototype mismatch using mod_perl by AlfaProject

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.