Debugging with PRINT Statements

BobDye

Since I couldn't get the debugging statements of BREAK (in various forms - they were either ignored or caused an error) to work, I opted to use PRINT at appropriate places in my program , to follow how some Do Loops were working. Once I understood, I commented the PRINT statements and, Lo, the program ceased to work BUT when I uncommented a PRINT statement - it ran!!!!! What a language...

mcc

OOps... Sorry, I didn't see your post until after I posted an answer to your earlier post. If these posts were stung together as a thread perhaps I would have seen your solution.

I'm not sure I follow exactly what you did.

You put in a PRINT statement (not a BREAK) inside a DO LOOP , then you remmed out the PRINT statement and that stopped the program? Then after un-remming the PRINT statement, it ran, correctly? Was the DEBUG ON in effect?

I put PRINTs inside DO LOOPS all the time, and comment them in and out, and have never observed any such behavior as that. What else was in there that did/did not get remmmed out?

Regards,
Mike C.

BobDye

Hi Mike,

Thanks for your very thoughtful response. I successfully used TB, decades ago, in my job and even won third place in the first programming contest!! Now retired, (and several other programing languages later)I thought I would try my hand in writing some simple programs to solve the some of the little puzzles which appear in the Sunday newspaper supplements. Then I started finding so many bugs in the TB programming which didn't exist decades ago. You've mentioned two - BREAK and CHAIN, but the one I just encountered was too mystifying. When I remmed out a PRINT statement, my program didn't run - when I un-remmed, it ran!!! No errors appeared - compiles fine, both times.

Yours,

Bob