On 2/21/07, Nicholas Geti <[EMAIL PROTECTED]> wrote: > > > Funny, when I tell Fox Folk that I do most of my debugging in Python > > by adding 'print' statements in critical places, they look at me as > > though I was advocating going back to punched cards. Glad to hear > > that someone else appreciates this technique! > > > > -- Ed Leafe > > -- http://leafe.com > > -- http://dabodev.com > > > > For most of my career I have sprinkled 'print/display' statements throughout > my code to trace where it is going. Sometimes I would just display on the > screen; other times print on paper. When I used to work in Fortran before > IDEs were invented, it was the only way to go. Even with IDEs it was > cumbersome to set up breakpoints, list variables to look at and then attempt > to trace run-time behavior. It was especially difficult when large loops had > to be debugged and you missed a branch and had to do it over.
On the Commodore Amiga the power light was controllable via software. Handy for debugging low-level code! -- Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
