This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Debugging Apache::ASP
From: "Differentiated Software Solutions Pvt. Ltd.," <diffs@vsnl.com>
Date: Wed, 6 Dec 2000 15:29:09 +0530
We've been using Apache::ASP over the past one month.
We are having problems debugging an ASP program.
We have set the debug level to 3 but still.....
At debug level 3, the line in which the error occurs is displayed.
But if we have multiple statements withing <% and %> tags then, the =
error display only gives only one line number (line number of the first =
statement) is displayed. We are finding it very difficult to identify =
the exact line where the error has occured.
In general we find Apache::ASP support for debugging quite poor. Are =
there any tools which we are missing out ??
How do others tackle this ??
How do people track "use of uninitialised variable".
===
Subject: Re: Debugging Apache::ASP
From: Stas Bekman <stas@stason.org>
Date: Wed, 6 Dec 2000 12:15:20 +0100 (CET)
On Wed, 6 Dec 2000, Differentiated Software Solutions Pvt. Ltd., wrote:
> Hi,
>
> We've been using Apache::ASP over the past one month.
> We are having problems debugging an ASP program.
> We have set the debug level to 3 but still.....
>
> At debug level 3, the line in which the error occurs is displayed.
> But if we have multiple statements withing <% and %> tags then, the error display only gives only one line number (line number of the first statement) is displayed. We are finding it very difficult to identify the exact line where the error has occured.
> In general we find Apache::ASP support for debugging quite poor. Are there any tools which we are missing out ??
>
> How do others tackle this ??
> How do people track "use of uninitialised variable".
use Carp ();
$SIG{__WARN__} = \&Carp::cluck;
===
Subject: Re: Debugging Apache::ASP
From: Joshua Chamas <joshua@chamas.com>
Date: Wed, 06 Dec 2000 13:30:40 -0800
Differentiated Software Solutions Pvt. Ltd.," wrote:
>
> Hi,
>
> We've been using Apache::ASP over the past one month.
> We are having problems debugging an ASP program.
> We have set the debug level to 3 but still.....
>
> At debug level 3, the line in which the error occurs is displayed.
> But if we have multiple statements withing <% and %> tags then, the error display only gives only one line number (line number of the first statement) is displayed. We are finding it very difficult to identify the exact line where the error has occured.
> In general we find Apache::ASP support for debugging quite poor. Are there any tools which we are missing out ??
>
> How do others tackle this ??
> How do people track "use of uninitialised variable".
>
Don't do "use strict", do PerlSetVar UseStrict 1. Use Apache::ASP v2.03
or greater as it had significant debugging enhancements. If
you are having problem with your debug output, let me see it,
and I may be able to help interpret. The line numbers are usually
right on.
===
Subject: Re: debuggers
From: martin langhoff <martin@scim.net>
Date: Thu, 07 Dec 2000 16:53:46 -0300
Perrin,
In fact, I've always been coding from NT machines -- for my *nix
servers, of course. Now the ActiveState people are building a
cross-platform and cross-language IDE that integrates with perldebug
nicely -- or so it seems. I'm actually starting to like it -- it's built
on top of mozilla, so its a bit bloated and slow -- but I like it, just
like mozilla ;)
And, on top of that, it's called Komodo, and that means 'comfort' -- in
Spanish, that is.
All this talk about DDD is making me wonder if there is a suitable
(graphical) Perl IDE that I can run on Gnome. If there's one, maybe I'll
change my dev workstation from an NT box to RHLinux 6.1 ...
Well, there's Komodo, for instance ;)
martin
pd: of course, in Spanish you'd say c