Be aware that inheritance is not determined at compile-time. When you do $obj->method(ARGS), what you're actually doing is $obj->can('method')->(ARGS). can() looks something like this: 
sub can {
    my ($self, $meth) = @_;
    my $class = ref $self || $self;
    my $subref = *{$class . '::' . $meth}{CODE};
    return $subref if defined $subref;
    for (@{$class . '::ISA'}) {
        $subref = $_->can($meth);
        return $subref if defined $subref;
    }
    return undef;
}

[download]
There's a lot of error-handling I've skipped, both in the definition of can() and the "expanded code" ($obj->can('method')->(ARGS)). The point is, you can modify @ISA at any time; there is no compile-time method resolution.

In reply to Re: debug at compile time by ursus
in thread debug at compile time by Anonymous Monk

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.