Comments on: MXMLC WTF (7): Snooping with verbose stacktraces http://blog.iconara.net/2007/11/22/mxmlc-wtf-7-snooping-with-verbose-stacktraces/ Sun, 07 Mar 2010 14:29:15 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: tom http://blog.iconara.net/2007/11/22/mxmlc-wtf-7-snooping-with-verbose-stacktraces/comment-page-1/#comment-7911 tom Thu, 10 Sep 2009 13:47:05 +0000 http://blog.iconara.net/2007/11/22/mxmlc-wtf-7-snooping-with-verbose-stacktraces/#comment-7911 <p>optimize is enabled per default. you have to disable it to see a difference.</p> optimize is enabled per default. you have to disable it to see a difference.

]]> By: Jeff Carnes http://blog.iconara.net/2007/11/22/mxmlc-wtf-7-snooping-with-verbose-stacktraces/comment-page-1/#comment-7706 Jeff Carnes Mon, 22 Dec 2008 12:45:14 +0000 http://blog.iconara.net/2007/11/22/mxmlc-wtf-7-snooping-with-verbose-stacktraces/#comment-7706 <p>It sounds like you did your testing with compc and not mxmlc (which has different defaults). If that's the case, compc defaults "debug" to true (mxmlc does not). As per the docs:</p> <p>"If you set this option to true, Flex also sets the verbose-stacktraces option to true"</p> <p>Try setting "debug" to false and you'll notice that the stack traces are a bit less revealing now and the file size will be about 33% smaller in part because it's not including line numbers and file names.</p> <p>"optimize" also defaults to true, so compiling with optimize=true is no different than compiling without specifying optimize. The docs don't state it, but I believe optimize is also affected by debug so with debug defaulting to true it might force optimize to false (even if you specify it). If I remember correctly, taking a debug SWF and running it through Adobe's optimizer app in the SDK results in a SWF identical to debug=false, optimize=true which makes me believe debug and optimize may be mutually exclusive.</p> It sounds like you did your testing with compc and not mxmlc (which has different defaults). If that’s the case, compc defaults “debug” to true (mxmlc does not). As per the docs:

“If you set this option to true, Flex also sets the verbose-stacktraces option to true”

Try setting “debug” to false and you’ll notice that the stack traces are a bit less revealing now and the file size will be about 33% smaller in part because it’s not including line numbers and file names.

“optimize” also defaults to true, so compiling with optimize=true is no different than compiling without specifying optimize. The docs don’t state it, but I believe optimize is also affected by debug so with debug defaulting to true it might force optimize to false (even if you specify it). If I remember correctly, taking a debug SWF and running it through Adobe’s optimizer app in the SDK results in a SWF identical to debug=false, optimize=true which makes me believe debug and optimize may be mutually exclusive.

]]>