Comments on: Lost in Debug Hell : Fix Your Messy Trace Commands! http://cheezeworld.com/better-debug-tracing/ The Cheeze to Your Macaroni - Games, Open Source Programming, and Other Odd Ramblings. Fri, 05 Mar 2010 11:04:39 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Scott Delamater http://cheezeworld.com/better-debug-tracing/comment-page-1/#comment-50 Scott Delamater Tue, 03 Jun 2008 15:31:10 +0000 http://cheezeworld.com/?p=36#comment-50 err...what looks like: trace(""); in the prev comment should be: trace("<MyClass.myComplexFunction()>"); err…what looks like:

trace(“”);

in the prev comment should be:

trace(“<MyClass.myComplexFunction()>”);

]]> By: Scott Delamater http://cheezeworld.com/better-debug-tracing/comment-page-1/#comment-49 Scott Delamater Tue, 03 Jun 2008 15:26:29 +0000 http://cheezeworld.com/?p=36#comment-49 Excellent point! This alone can save someone hours of work. A related convention I use in cases where I may be debugging a particularly complex function (i.e., many trace statements in one function) is to trace the class/method name once, then indent subsequent trace statements: ... public function myComplexFunction ():void { trace( "" ); // crazy stuff happens here trace( "\tmyValue: "+myValue ); trace( "\tmyOtherValue: "+myOtherValue ); } ... Excellent point! This alone can save someone hours of work.

A related convention I use in cases where I may be debugging a particularly complex function (i.e., many trace statements in one function) is to trace the class/method name once, then indent subsequent trace statements:

…
public function myComplexFunction ():void
{
trace( “” );
// crazy stuff happens here
trace( “\tmyValue: “+myValue );
trace( “\tmyOtherValue: “+myOtherValue );
}
…

]]>