Chris Travers wrote:
> There are a few options for debugging the software, and some of them
> require more knowledge of the code than others.
>
> The first option (requiring less knowledge) is to use the following
> information to pull state info in the CGI app:
> 1) print STDERR
> 2) $form->d
There are a few options for debugging the software, and some of them
require more knowledge of the code than others.
The first option (requiring less knowledge) is to use the following
information to pull state info in the CGI app:
1) print STDERR
2) $form->debug
3) $form->error
The second opt
herman vierendeels wrote:
> you can add
>
> print STDERR "$this_or_that";
>
> statements to the code.
>
> Output can then be read in
> /etc/httpd/logs/error_log
Thanks,
No single step eh?
My last major coding was done using Catalyst. I got spoiled a bit. I
could run the Catalyst test serv
you can add
print STDERR "$this_or_that";
statements to the code.
Output can then be read in
/etc/httpd/logs/error_log
Herman Vierendeels
2009/3/1 Roderick A. Anderson :
> I've run into a problem (which I started in the -users list) where
> ledgersmb is installed in a created schema (ledgersm
