Re: AW: AW: AW: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-08 Thread Alex Harui
On 5/8/16, 4:34 PM, "Christofer Dutz" wrote: > >Well I agree that it would be good to share instances of things, but not >configuration. Especially not sharing stuff between different instances >of different compilers. Just as an example: MXMLJSC sets a different >backend then COMPJSC does ...

AW: AW: AW: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-08 Thread Christofer Dutz
___ Von: Alex Harui Gesendet: Sonntag, 8. Mai 2016 16:15:57 An: dev@flex.apache.org Betreff: Re: AW: AW: [FLEXJS] Probably found the reason for some of my problems ... On 5/8/16, 5:21 AM, "Christofer Dutz" wrote: > >Hi Alex, > >well actually the Ant build doesn&

Re: AW: AW: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-08 Thread Alex Harui
On 5/8/16, 5:21 AM, "Christofer Dutz" wrote: > >Hi Alex, > >well actually the Ant build doesn't destroy the compiler, but the entire >VM. To me it seems that for every compilation and every Unit test a new >VM is forked. This is extremely expensive and time consuming. If you have >a look at the

AW: AW: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-08 Thread Christofer Dutz
flex.apache.org Betreff: Re: AW: [FLEXJS] Probably found the reason for some of my problems ... On 5/7/16, 12:01 PM, "Christofer Dutz" wrote: > >I agree that the initial version doesn't have to be perfect. But we have >to keep track of such places and make sure to clean

AW: AW: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-08 Thread Christofer Dutz
ow-is-javas-threadlocal-implemented-under-the-hood Von: Alex Harui Gesendet: Sonntag, 8. Mai 2016 07:23:43 An: dev@flex.apache.org Betreff: Re: AW: [FLEXJS] Probably found the reason for some of my problems ... On 5/7/16, 12:01 PM, "Christofer Dutz"

Re: AW: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-07 Thread Alex Harui
On 5/7/16, 12:01 PM, "Christofer Dutz" wrote: > >I agree that the initial version doesn't have to be perfect. But we have >to keep track of such places and make sure to clean them up as soon as we >have some time. Perhaps it would be a good idea if implementing something >we know is hacky, to c

Re: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-07 Thread Harbs
; > Von: Josh Tynjala > Gesendet: Samstag, 7. Mai 2016 20:36:41 > An: dev@flex.apache.org > Betreff: Re: [FLEXJS] Probably found the reason for some of my problems ... > > Judging by the comments in the file, Mike meant to get rid of this cla

AW: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-07 Thread Christofer Dutz
akpoint. Chris Von: Josh Tynjala Gesendet: Samstag, 7. Mai 2016 20:36:41 An: dev@flex.apache.org Betreff: Re: [FLEXJS] Probably found the reason for some of my problems ... Judging by the comments in the file, Mike meant to get rid of this class. I'm guessing it was added as a temporary h

Re: [FLEXJS] Probably found the reason for some of my problems ...

2016-05-07 Thread Josh Tynjala
Judging by the comments in the file, Mike meant to get rid of this class. I'm guessing it was added as a temporary hack to get things up and running as quickly as possible, which was a very important thing earlier in the life of FalconJX. Sometimes, things that we know are "super-duper-ultra-bad" a

[FLEXJS] Probably found the reason for some of my problems ...

2016-05-07 Thread Christofer Dutz
Ok ... in a final struggle to at least have something to show at my talk at ApacheCon I dug really deep into the compiler and noticed one thing: There's a class called: JSSharedData, which contains a set of public static variables for containing the state of a compilation (I guess). The problem