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 ...
___
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&
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
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
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"
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
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 create an Issue for cleaning up?
It's just that trac
