Makes sense. I remember thinking along the same lines as Andrés, but getting rid of the empty ctor functions ( http://code.google.com/p/google-web-toolkit/wiki/ClassSetupAndInstantiationOptimization) will probably obviate it, as few if any classes have truly empty ctors.
On Thu, Jul 2, 2009 at 7:09 PM, Scott Blum <[email protected]> wrote: > Of course, if we go with the idea of hoisting Java constructors into the > JavaScript constructor, that stops working. > Speaking of which, we don't have to limit it to just classes with one live > constructor... two different JS constructors can share the same prototype > object. > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
