By having the linter make the giant assumption that all subs are methods, that tells you a bit about $self, but not enough. It only helps determine that cases such as the following aren't problems: 

{   package Base;
    sub x { ... }
}

{   package Child;
    our @ISA = 'Base';
    sub y { shift->x }
}

[download]

However, it doesn't help determine that something is a problem. For example, is there a problem in the following? 

package Package;
sub y { shift->x }

[download]

No, turns out package Package is just a role: 

{   package SomeRole;
    # Implementor must provide y
    sub y { shift->x }
}

{   package Class;
    our @ISA = 'SomeRole';
    sub x { ... }
}

[download]

But that's not the real test. How often do you call a child method that doesn't exist? I expect the majority of problems to be in code such as the following: 

sub some_method {
    my ($self, $arg) = @_
    ...
    $arg->other_method();
    ...
}

[download]
or 
sub some_method {
    my ($self) = @_
    ...
    $self->attribute->other_method();
    ...
}

[download]

The linter knows absolutely nothing about the class or object whose method other_method is being called, so it has no idea if other_method exists for that class or object.

In reply to Re^3: linting for undefined object methods by ikegami
in thread linting for undefined object methods by aespen

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.