If you set the prototype of your mock sub before replacing the original one, that should get rid of the warning, try commenting out the set_prototype call in the following and you should get the "Prototype mismatch" warning back:

use warnings;
use strict;
use Scalar::Util qw/set_prototype/;

sub foo ($$$) { print "foo(@_)\n" }

foo(1,2,3);  # prints "foo(1 2 3)"
{
        my $name = "foo";
        my $sub = sub { print "bar(@_)\n" };
        set_prototype(\&$sub,prototype($name));
        #use Devel::Peek; Dump($sub);
        no strict 'refs';
        no warnings 'redefine';
        *$name = $sub;
}
foo(4,5,6);  # prints "bar(4 5 6)"

[download]

By the way, in the code you showed, you're disabling strict 'refs' for a fairly large block of code.

In reply to Re: Prototypes required even after mocking a sub by haukex
in thread Prototypes required even after mocking a sub by stevieb

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.