> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Ed Leafe > Sent: Tuesday, February 20, 2007 6:45 PM > To: [EMAIL PROTECTED] > Subject: Re: Tracing (somebody else's) program flow tricks > > On Feb 20, 2007, at 8:10 PM, Whil Hentzen (Pro*) wrote: > > > debugo is one of the top ten improvements to the language since they > > added that third work area. <s> > > 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 >
When I deploy something new that is mission critical, I load up a string during execution and output it at the end. I name it the same as the prg or class followed by ".log". Sometimes I count something or display the contents of a variable; basically anything you would put in a wait window or a "?" followed by a crlf. I use STRTOFILE() to output the text. I can view these files on customers' computers. Jeff Jeff Johnson [EMAIL PROTECTED] 623-582-0323 Fax 623-869-0675 --- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/x-pkcs7-signature --- _______________________________________________ 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.
