On Sun, Nov 1, 2009 at 10:38 AM, Bart Guijt <[email protected]> wrote:
> Although I concur with Bob Vawter's comment, I still think there's a > place for a compiler transformation like this. The proposal is not to > meet incompetence levels of Java programmers, it is to enable existing > Java libraries in GWT client code (AFAIC). > I think that is precisely the reason you don't want to allow it -- existing libraries are written with the implicit assumption that such calls are synchronous. The whole idea behind runAsync is that by explicitly specifying where the split point happens, the programmer can structure the code better to handle the load there, the associated delay, and possible failures. You can see the problems MS has had trying to transparently turn synchronous calls into asynchronous ones first with Volta and then another attempt I can't find the name of quickly. Also, it isn't just this method that would have to be written to pass a continuation but everything on the callstack, and if just one such method were possibly called basically the entire program would have to get transformed. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
