atom feed36 messages in org.apache.incubator.flex-devRe: Trace & Log
FromSent OnAttachments
Martin HeideggerJan 19, 2012 9:37 am 
Omar GonzalezJan 19, 2012 9:40 am 
Skogen, EspenJan 19, 2012 9:45 am 
Martin HeideggerJan 19, 2012 9:51 am 
Arnoud BosJan 19, 2012 9:55 am 
Rui SilvaJan 19, 2012 9:57 am 
Petr CihelkaJan 19, 2012 10:01 am 
Martin HeideggerJan 19, 2012 10:02 am 
Omar GonzalezJan 19, 2012 10:04 am 
Alex HaruiJan 19, 2012 10:06 am 
Martin HeideggerJan 19, 2012 10:20 am 
Omar GonzalezJan 19, 2012 10:28 am 
Martin HeideggerJan 19, 2012 11:10 am 
Alex HaruiJan 19, 2012 11:31 am 
Martin HeideggerJan 19, 2012 12:02 pm 
Martin HeideggerJan 19, 2012 12:04 pm 
Alex HaruiJan 19, 2012 12:33 pm 
Roland ZwagaJan 19, 2012 1:52 pm 
Martin HeideggerJan 19, 2012 7:08 pm 
saurabh jainJan 19, 2012 10:28 pm 
Martin HeideggerJan 19, 2012 10:36 pm 
Alex HaruiJan 19, 2012 10:42 pm 
saurabh jainJan 19, 2012 10:44 pm 
Martin HeideggerJan 19, 2012 11:33 pm 
saurabh jainJan 19, 2012 11:43 pm 
Martin HeideggerJan 19, 2012 11:51 pm 
saurabh jainJan 20, 2012 12:17 am 
Dirk EismannJan 20, 2012 12:42 am 
Martin HeideggerJan 20, 2012 12:46 am 
Dirk EismannJan 20, 2012 6:42 am 
Martin HeideggerJan 20, 2012 6:59 am 
Roland ZwagaJan 20, 2012 7:03 am 
Dirk EismannJan 20, 2012 7:12 am 
Roland ZwagaJan 20, 2012 7:25 am 
Martin HeideggerJan 25, 2012 12:52 am 
Alex HaruiJan 25, 2012 2:06 pm 
Subject:Re: Trace & Log
From:Alex Harui (aha@adobe.com)
Date:Jan 19, 2012 12:33:25 pm
List:org.apache.incubator.flex-dev

On 1/19/12 12:02 PM, "Martin Heidegger" <mh@leichtgewicht.at> wrote:

On 20/01/2012 04:32, Alex Harui wrote:

The injection of data that is fixed from the time of compilation (not before) is a reasonable thing to be added to a compiler. Why? Because it bloats code a lot more if it has to be by hand (seeing all the log = Log.getLogger() statements). In general I think AS3 can become a thinner, faster and easier to use language with this construct, as any workaround to the problematic of compilation data results in a lot of code.

I'm still looking for the use case. Do you just want release player performance profiling?

I would think these kinds of compiler features would run into the "library problem". Right now, for compilation speed, the framework is compiled into a SWC. Would you have this extra code in the SWC or not? If not, then do you ship two versions of the SWC? And then, when someone wants to do another compiler feature, do you add more libraries for each combination?

If you start packing all of this stuff into one library, the default SWC is fat and slow. You can ask a post-link optimizer to clean out what you don't want, but that also slows down compilation time.