you can use a perl-parser to find all calls and eval{} them.

E.g. I have a patch of B::Deparse which extracts all such calls, but this opens new problems since compiling perl involves executing BEGIN{} blocks.

IIRC there are also moduls in CORE to parse packages like etags and ctags do.¹

Cheers Rolf

UPDATES:

1) I was thinking of B::Xref 

~:/tmp$ cat tst.pl
foo();
 
sub foo { print }
foo();
~:/tmp$ perl -MO=Xref,-d tst.pl 
File tst.pl
  Subroutine (main)
    Package main
      &foo              &1, &4
tst.pl syntax OK
~:/tmp$

[download]

so you can find all calls, now you just have to check the STASHes in a BEGIN Block.

HTH!

In reply to Re: Detecting undefined subroutines at compile time 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.