Philippe M . Chiasson wrote:
> On Mon, Sep 24, 2001 at 11:48:44PM +0800, Stas Bekman wrote:
>
>>Where do we put debug functions? debugger doesn't really help in dumping
>>complicated data structures like apr_table_t.
>>I guess I can also think of .gdbinit macro to do the same or even based
>>on this function.
>>
>
> How about stuffing them all in modperl_debug.[hc] and make sure all call
> to stuff in there is wrapped in a DEBUG() macro ? That way, all that stuff
> goes in when MP_DEBUG=1, but vanishes otherwise.
+1 for modperl_debug.[hc]
-1 for leaving debug prints around.
We already have debug functionality you are talking about using the
tracing facility, which you can configure on and off for very specific
modes only. So no need for DEBUG.
I'm talking here about having a set of helper functions, that do things
like Data::Dumper, per my example function I've sent, to be used mainly
during development, when it's not easy to look at complicated structures
and similar.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
