On 5/8/16, 4:34 PM, "Christofer Dutz" <christofer.d...@c-ware.de> 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 ... sharing breaks things here. Agreed. In Falcon, I think the Workspace is intended to share things common to all Projects. AIUI, each Project has its own compiler and configuration. Looks like there is some clean up to do. I think we should be able to reference the Project instance from most places in the compiler now. > >In Ant you do fork="yes" but forkMode="perBatch" so I guess you end up >with one VM for the unit and one for the integration-tests. maven >currently runs both in the VM of the build (default setting which is >highly efficient). > >Talking about performance, I would opt to still make things maintainable >and debuggable at the cost of a tiny bit of performance and pay the costs >by fixing some other performance problems instead. For example by using >some unsynchronized versions of containers instead of synchronized >versions (Sonar is complaining greatly about this). And the cost of >having a base set of interfaces that both implementations share and to >have specialized interfaces that extend these to allow optimizations. How >about that? So for example have an IElement which is used throughout the >code and then there's a IJsElement which extends IElement and provides >access to some JS specific stuff, that the rest of the application >doesn't need to know about. I'm not quite sure what classes you are referring to here, but it sounds reasonable. -Alex
