> > > My point is simply if the Java->JS compiler is moving to separate > compilation, > Well, that is why we are having this discussion.
> having hooks in it cannot help you if the things you want require > whole-world analysis. > It actually can, as I noted above, saving duplication of configuration processing. Otherwise, yes, I could do some global analysis. > If the reachability analysis is done at a later "linking" stage, then > clearly that cannot be available at the compilation stage. > Again, that is why we are having this discussion. I need to be able to do reachability analysis together with the code generation ne to have any chance of this performing well. And the problem is that if code gen must happen before J2CL and reachability analysis and optimization later then this can't really be done. Now, I am not saying that J2CL has to do the reachability analysis - but I need to be able to do it at the right time within it. > So I think what you want is fundamentally incompatible with the separate > compilation direction. That means that either GWT3 is not for you or you > will have to build an external tool that basically does much of what the > existing GWT compiler does now to get what you want. > Hence all my comments. Why should GWT3 go into such a direction that it makes it incompatible for me, an existing GWT user, or for any existing GWT user. Sure, it can split things away, but it can allow things to be done externally. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/122671f7-1ad6-462e-8c4a-369574362cba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
