> -----Original Message----- > From: Martin Heidegger [mailto:m...@leichtgewicht.at] > Sent: Wednesday, January 25, 2012 12:53 AM > To: flex-dev@incubator.apache.org > Subject: Re: Trace & Log > > Hey there, > > I just took a little time and ran some tests with flash.trace.Trace. It > is not > suitable for logging because it doesn't reveal how far down the rabbit > hole > (stack) the method has been called from, ergo: we cant find out which > method called logging. And even if it would have: Having no runtime > support is also a dealbreaker and the chances are high that it would > have been slower if you used this method for every call rather than a > exception just for the logging calls. > > http://www.leichtgewicht.at/862/flash-trace-trace-in-depth/ > > yours > Martin. > My tracing profiler prototype uses a Error to get a starting stack trace.
I agree the callback can degrade performance. The question for me is what penalty, if any, we want to impose on the way we write our code or the output SWF for the low-probability but high-value of debugging a problem in the wild. Alex Harui Flex SDK Developer Adobe Systems Inc. Blog: http://blogs.adobe.com/aharui
