just found that B::Xref lists sub-calls and(!) sub-definitions:
perl -MO=Xref tst.pl |grep foo tst.pl syntax OK &foo s1 &foo &1, &4 Subroutine foo

so just needing to parse¹ and compare the output.

But I agree that the dynamic nature of Perl makes such static parsing look strange.

Cheers Rolf

1) especially the raw output could be easily processed:

$ perl -MO=Xref,-r tst.pl |grep foo tst.pl (definitions) 1 main & foo + subdef tst.pl syntax OK tst.pl (main) 1 main & foo + subused tst.pl (main) 4 main & foo + subused tst.pl foo 3 main $ _ + used $ cat tst.pl foo(); sub foo { print } foo();

In reply to Re^3: Detecting undefined subroutines at compile time (B::Xref) by LanX
in thread Detecting undefined subroutines at compile time by bdenckla

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.