I stand very much corrected. /hat tip/
I suppose I've already been using JsType so much it has begin to cloud my
judgement.
Hm. How ironic that the only methods unreachable to reflection-via-jsni
would be private jsni methods? :-)
--
You received this message because you are subscribed to
I suppose I technically have access to the AST nodes... If I *really *wanted
to I could probably find a way, but that would be exceptionally nasty, so,
no thanks...
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this
Getting offtopic, but there is absolutely no requirement that JSO methods
are public. See dom.client.Element for several examples of private methods.
On Mon, Mar 30, 2015 at 10:27 PM James Nelson ja...@wetheinter.net wrote:
Ok, great. Thanks for the heads up. I was pretty sure that Strings
Same also applies to JSOs. (i.e. You cannot call JSO methods with JSNI).
On Mon, Mar 30, 2015 at 9:06 AM, 'Roberto Lublinerman' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
GWT strings and arrays are JS native strings and arrays (no prototype
monkey patching),
Please file an issue to keep track.
On Mon, Mar 30, 2015 at 9:06 AM, Roberto Lublinerman rlu...@google.com
wrote:
GWT strings and arrays are JS native strings and arrays (no prototype
monkey patching), in Java code calls to Object, String, Array and
Comparable methods are devirtualized if
GWT strings and arrays are JS native strings and arrays (no prototype
monkey patching), in Java code calls to Object, String, Array and
Comparable methods are devirtualized if applied to instances typed at one
of those types.
So the answer is yes: You wont be able to call instance methods this
