"be consistent" | |
PerlMonks |
Turning on debug/verbosity in modules that are sub-calledby hacker (Priest) |
on Feb 25, 2005 at 00:29 UTC ( [id://434324]=perlquestion: print w/replies, xml ) | Need Help?? |
hacker has asked for the wisdom of the Perl Monks concerning the following question: I've banged my head against the desk so many times this month on this one issue, that there's a dent there now. This SoPW is the result of that frustration hitting me over and over and over. I seem to be running into a streak of issues where modules that I'm using, are using other modules, which are throwing errors and warnings that I need to debug. I started seeing it with XML::RSS::Tools throwing errors in XML::Parser, several other XML and RSS-related modules, and now moments ago, Net::NNTP is throwing errors down in Net::Cmd. Here's an example of the errors/warnings I see:
My code is always run with warnings, diagnostics, and strict.. and for most of my test runs, it runs perfectly clean. Except when it throws these. In this case, it must be something in the article body that Net::Cmd doesn't like, and it errors out. How can I start flipping on some more-verbose debug in these sub-called modules, if I'm not calling them directly? Some modules support a Debug() method, some do not, so I'm stuck. I don't want to modify the default methods of these modules themselves (i.e. by editing the .pm file). Is there another way?
Back to
Seekers of Perl Wisdom
|
|