John Doe wrote:
> An easy quick and dirty way to find out where your code stucks is by putting > warns (go to the error log) or prints (go to browser) after every statement > in the code. warns are nice cause they go to the error log rather than waiting on the browser to receive and display. But even better is to step through the code with the Perl debugger - http://perl.apache.org/docs/1.0/guide/debug.html#Interactive_mod_perl_Debugging -- Michael Peters Developer Plus Three, LP
