Another approach is to add another level into the hash: 
package FunnyEmail;
use strict;
use warnings;
use Email::Simple;

sub new {
    my $class = shift;
    my $simple = Email::Simple->new(...);
    my $self = {simple => $simple};
    bless $self, $class;
}

[download]
Now, you have to redirect all the methods of Email::Simple into the subhash: 
our $AUTOLOAD;
sub AUTOLOAD {
    my $self = shift;
    my $simple = $self->{simple};
    my $method = (split /::/, $AUTOLOAD)[-1];
    if ($simple->can($method)) {
        $simple->$method(@_);
    } else {
        die "Cannot run $method\n";
    }
}

[download]

In reply to Re: avoiding overwriting variables in an inherited class by choroba
in thread avoiding overwriting variables in an inherited class by whatnext156

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.