If you blanket replace P with printf STDERR and change Ehv to a direct access, you have you wish:

#!/usr/bin/perl 
use warnings; use strict;

{ package pkg;  use warnings; use strict;
  our $cnt=0;

  sub new     { my $p = shift; my $c = ref $p || $p;
                printf STDERR "pkg %s created\n", ++$cnt; 
                $p = bless { cnt => $cnt, fnc => 
                     sub { my $p2 = ref $_[0] ? shift : __PACKAGE__;
                           printf STDERR "fnc %d calling %s\n", $cnt, 
+$p2->FUNC;
                           undef;
                         } }, $c;
              }
  
  sub destroy { printf STDERR "pkg %s(%s) destroyed\n", $cnt, $_[0]->{
+cnt}; undef }
  sub DESTROY { goto &destroy }
}

package main;

sub callfunc(;$$);  #silence warn about proto not ready
sub callfunc (;$$) {
  my $p = pkg->new;
  my ($callfunc, $recur) = @_;
  $callfunc||=0; $recur||=0;
  local * FUNC = sub () { printf STDERR "In FUNC, cnt=%s\n", $p->{cnt}
+; undef };
  FUNC() if $callfunc;
  callfunc($callfunc, $recur) if $recur && $recur--;
}

callfunc;
callfunc 1;

callfunc 0,1;
callfunc 1,1;

pkg::destroy
[download]

And you get the similar output with 2 subs in a text editor. inserting print STDERR for all of the Pe's and an extra '\n' for at the end of all strings. And a removal of the null pointer deref which isn't even used. But you still get an undef warning.

pkg 1 created
pkg 1(1) destroyed
pkg 2 created
In FUNC, cnt=2
pkg 2(2) destroyed
pkg 3 created
pkg 4 created
Subroutine main::FUNC redefined at /tmp/tst2.pl line 27.
pkg 4(4) destroyed
pkg 4(3) destroyed
pkg 5 created
In FUNC, cnt=5
pkg 6 created
Subroutine main::FUNC redefined at /tmp/tst2.pl line 27.
In FUNC, cnt=6
pkg 6(6) destroyed
pkg 6(5) destroyed
Use of uninitialized value in printf at /tmp/tst2.pl line 16.
pkg 6() destroyed
[download]

Or you could spend 30 seconds and install the routines. They are simple routines and I explained my rationale for using them.

The differences in the final program are minor but I spend hours revising it in development where retyping pointless expansions is harmful and wasteful.

So if your help requires not being able to do 2 text subs or installing modules that do that for you automatically, then its obvious you are not someone I'd want creating toxic responses.

And before you claim you don't want to install modules that due unknown things -- they are simple modules, published on CPAN and backed by my name -- someone who is unafraid of signing it on their posts no matter how my post may make me look. It's called integrity and honesty.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.