From: David T-G <[EMAIL PROTECTED]>
> The recent post containing print statements "this is one" and so on
> reminded me of an old question that I've never had answered: what's a
> good way to trace your program as it runs, preferably without getting
> into the debugger?
You migh
At 07:31 AM 6/7/02 -0500, David T-G wrote:
>The recent post containing print statements "this is one" and so on
>reminded me of an old question that I've never had answered: what's a
>good way to trace your program as it runs, preferably without getting
>into the debugger?
You have to use the/a d
on Fri, 07 Jun 2002 12:31:52 GMT,
[EMAIL PROTECTED] (David T-G) wrote:
> The recent post containing print statements "this is one" and so
> on reminded me of an old question that I've never had answered:
> what's a good way to trace your program as it runs, preferably
> without getting into the
X %GIANT_MULTIDIMENSIONAL_HASH
X @some_stuff
> -Original Message-
> From: David T-G [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 07, 2002 8:32 AM
> To: perl beginners
> Subject: debugging statements and such
>
>
> Hi, all --
>
> The recent pos
ant to
move the code to production.
Rob
-Original Message-
From: David T-G [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 07, 2002 8:32 AM
To: perl beginners
Subject: debugging statements and such
Hi, all --
The recent post containing print statements "this is one" and so
Hi, all --
The recent post containing print statements "this is one" and so on
reminded me of an old question that I've never had answered: what's a
good way to trace your program as it runs, preferably without getting
into the debugger?
I realize that that's sort of a loaded question and that t
