comment on

But it would be nice if there was a way to catch such cases...

Well, you've answered your own question when you said:

"there could be autoloads providing the subroutine, or it could have been dynamically generated at runtime in an eval, or something. "

The flexibility of Perl comes with a price. This is one of them.

However, I would strongly disagree when you said:

without having to write a test suite that exercises every code branch, which isn't always (or even usually) possible.

If you can't test your code then something is wrong with it. Fix the design so you can test it. If you have problems doing this, then post a SOPW - I'm sure somebody could help ;-)

Seriously, 100% test coverage is an attainable goal with surprisingly little effort.

In reply to Re: When -w and use strict aren't enough... by adrianh
in thread When -w and use strict aren't enough... by RMGir

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks