Re^3: brian's Guide to Solving Any Perl Problem

Of course it's fine to save warn() for "real" error messages, but then the same could be said for only using print() for real output messages.

My problem, for which I'd welcome suggestions, is that I'm not familiar with how to use debug() in the midst of debugging a huge Tk-based application that I'm working on. The subroutines I am debugging get fired when I click one of the Tk buttons, and I know for sure that I can get at my warn() messages as above via my STDERR files. Out of ignorance, I'm just expecting use of debug() to be impractical.

Comment on Re^3: brian's Guide to Solving Any Perl Problem

Replies are listed 'Best First'.
Re^4: brian's Guide to Solving Any Perl Problem by brian_d_foy (Abbot) on Jul 26, 2004 at 07:02 UTC
The debug() function can be whatever you want it to be, because you have to write it. The print() loses against warn() because I can redefine the behaviour of warn() without changing the statements. -- brian d foy <bdfoy@cpan.org>	[reply]