Ok, great. Thanks for the heads up. I was pretty sure that Strings had become native first-class objects.
Since JSOs will all have public methods, I will be safe with the same fix for String (not using JSNI if not necessary). Given that java arrays only have one field, and that field does not work in JVM reflection, nor do any of the Object methods, I'll leave them alone (that's what java.lang.reflect.Array is for)... Added issue https://code.google.com/p/google-web-toolkit/issues/detail?id=9166 to track this. For posterity and search indexing, if anyone tries to use hashCode, equals or compareTo on String or Array in JSNI and are getting undefined reference errors, use a static method instead. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/9bbd9127-65c9-4fa1-9743-a94fcd4f3bf4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
