Thanks for the advice! I've submitted a patch for GWT-P so the code won't rely on the exception being thrown.
On Sep 19, 11:36 am, Thomas Broyer <[email protected]> wrote: > The JavaDoc says IndexOutOfBoundsException, so you shouldn't expect a more > specific exception. > > BTW, coding with exceptions is kind of an anti-pattern in JS (because it's > faster to check for good values beforehand than rely on exceptions being > thrown when bad values are passed in); this is kind of a shift from > "standard" Java development, but it's basically the same, and even stronger, > in GWT development: the Java runtime emulation does not necessarily throw > exceptions; sometimes you'll have a JavaScriptException instead (this is > even more true when you enable a few optimization switches, like > disableClassCastException). > > The rule of thumb is: do not count on exceptions being throw the same as in > a Java VM. You writing Java, you're reading Java, you're using Java tools, > but you're developping JavaScript running in a browser! > That's to say, it's highly likely that such a bug report would be closed as > WontFix. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
