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
I have to say this:
I thought debugging would be hard... and it really isn't, (for 90%
of the cases).
The most reason I have to debug is to see what my data structures look like
and what they contain at a part in my program.
My old method was:
local $" = "\n";
print "@stuff in here\n";
e
Well you could toy around with source filters. A source filter allows you
to manipulate your code after it is read into memory but before it is
executed.
Here is a good article on it, and even has an example of handling debug
output.
http://www.samag.com/documents/s=1287/sam03030004/
You could
