I am confused by your answer, when I try this:

{       
    eval "package $pkg;"; 
    no strict 'refs';
    *{$pkg . '::new'} = sub {        
        (shift)->SUPER::new(%{$fields}) 
    };
}
[download]

{
    no strict 'refs';
    *{$pkg . '::new'} = sub { 
        eval "package $pkg;";        
        (shift)->SUPER::new(%{$fields}) 
    };
}
[download]

Does the whole subroutine need to be eval-ed?

Does the whole subroutine need to be eval-ed?

Since "package" has lexical boundaries, yes.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

merlyn,

Thanks for the quick response. I tried this:

eval "package $pkg; sub new { (shift)->SUPER::new( \%\$fields ); }"
[download]

and got this:

Variable "$fields" will not stay shared at (eval 32) line 1.
[download]

Although the the 300+ tests passed, and if $fields was somehow lost, they would not have passed. Is this warning something I should worry about? Any idea as to what context $fields is not staying shared within?
-stvn

dragonchild figured it out, this code works.

eval "package $pkg; *new = sub { (shift)->SUPER::new( \%\$fields ); }"
[download]

It avoids the warnings, and all the tests pass. Thanks for the help.
-stvn