No, it's not Test::Class I'm carping about. Most of the time it's features I've wanted in Test::Class, not bug fixes.
As for detecting the broken functionality programmatically, the only thing I thought of was using B::Deparse to get the source code of the subroutine and create a digest for it after and compare that with the new sub. That involves embedding the digest and recreating if necessary. Also, just because the source code doesn't change doesn't mean the bug wasn't fixed elsewhere.
If I'm misunderstanding you or you have a better approach which doesn't involve running the code, please let me know. (Hmm, creating local test suites targeting external modules?)
Cheers,
Ovid
New address of my CGI Course.
In reply to Re^2: Upgrade-proofing overridden subroutines
by Ovid
in thread Upgrade-proofing overridden subroutines
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |