Howdy, >I agree that this debate will carry on forever, because we all work >differently. I believe having one trace level is good compromise. The >way I work is to put debug statements into the code to decipher what is >happening in the program flow, but I would love to have a trace level to >print out parameter values or variable values. The debug level gets >extremely verbose when logging out array values etc and all you are >interested in is program flow.
Interesting that the above is exactly the opposite of what Jeff's use-case is: trace for entering/exiting methods, debug for variable values ;) Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
