|
Scott:
The
are two keys to debugging: Watch what the machine does when the program is run
interactively. You will have limited control, of course, and
won't be able to single-step through your code, but you will be able to see
exactly the same things that BWS sees on the
screen.
T'other key is using way too many displays of information that is
"obvious". For example, instead of using
for debugging use something like
That way you'll be certain where you are in your logic.
Bruce has asked about cleaning out variables between events. Be
sure that you initialize all variables, whether you think they need to
be or not. Some languages try to be nice to you by not requiring that
you force strings to be empty, et cetera. Don't trust a program that
tries to be smarter than you are.
Pax,
Ernest 21 Oct 04
|
<<attachment: image001.jpg>>
