On Sat, Aug 10, 2013 at 4:42 PM, Brian Slesinsky <[email protected]>wrote:
> Now that I understand it (hopefully), I think Ray's proposal is a good way > to define new API's by writing Java wrappers that configure generated > objects at runtime. Adding parameters to GWT.create() calls seems somewhat > orthogonal as a way to pass arguments to generators at compile time. > > As often happens with language extensions, when you put them together, > things get more complicated but also more expressive; if GWT.create() takes > extra arguments then these should also be literals that you can accept in a > user-defined create method. > It doesn't have to all be literals -- you could imagine that the generator would be able to accept them as constructor arguments for the generated class. Of course, specifying which can be expressions and which must be literals (or things the compiler can compute at compile time, perhaps even inlining calls to get to the literal), and doing that in such a way to get good feedback to the developer isn't trivial. -- John A. Tamplin -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
