On Tue, Oct 15, 2013 at 8:18 AM, John A. Tamplin <j...@jaet.org> wrote:
> You could make this completely foolproof by introducing an extra step - > add a new wrapper type GwtInt which behaves just like Integer except it > isn't autoboxed. Then have toInt32(GwtInt), and fix all the compile errors > to include that call. Then replace GwtInt with double everywhere. > That begs the question though, doesn't it? :) The steps I outlined are how I'd cope with the return type changing from "int" to "double" without ever introducing compile errors and without needing to submit any global cleanup changelists. Adding a GwtInt intermediary step means needing to instead cope with converting the return type from "int" to "GwtInt" and then again from "GwtInt" to "double", which each seem as hard if not harder than the original problem. -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
