On 5/7/16, 12:01 PM, "Christofer Dutz" <christofer.d...@c-ware.de> 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 create an Issue for cleaning up? > >It's just that tracking down stuff like this comes close to being >impossible. I was confused why the backend I put in when creating the >COMPJSC instance wasn't there when using it. I could only track that down >by using an insanely expensive property-access-breakpoint. Just curious, what is the advantage of creating instances of every tool in the group? I'm not clear it was intended for sharing between instances of the compiler, just for sharing data from various places in the compiler. I'm not a Java VM expert, but I think when we do builds we create an instance of the compiler, compile something, destroy that instance, create another instance, compile that next thing, etc. Which is pretty much what would happen on the command-line. Are you trying to keep certain things in memory so the start up doesn't have to happen every time, sort of like fcsh? Thanks, -Alex
