Re: working in beta but not in latest git

2016-08-10 Thread Vassilis Virvilis
@Jens thanks that worked (compiled) with the minimal diff - just an extra set of parentheses. I am keeping from the discussion - that this isn't needed any more since Boolean is a mapped native js type and that specific code will never enter the third clause of the if. @Paul, @Jens thanks also

Re: working in beta but not in latest git

2016-08-09 Thread Jens
> From my understanding (which is not much) the whole point is moot. Looks > like java Boxed types (Boolean, Double, Integer) are mapped directly to JS > primitives so the need for the above code is gone. Is that right? > Yes but only Boolean, Double and String are mapped. > If yes and

Re: working in beta but not in latest git

2016-08-09 Thread Paul Stockley
Your assumption is true for Boolean and Double but not the other boxed types. On Tuesday, August 9, 2016 at 10:39:53 AM UTC-4, Vassilis Virvilis wrote: > > From my understanding (which is not much) the whole point is moot. Looks > like java Boxed types (Boolean, Double, Integer) are mapped

Re: working in beta but not in latest git

2016-08-09 Thread Vassilis Virvilis
>From my understanding (which is not much) the whole point is moot. Looks like java Boxed types (Boolean, Double, Integer) are mapped directly to JS primitives so the need for the above code is gone. Is that right? If yes and just for the shake of syntax curiosity: what is the correct syntax to

Re: working in beta but not in latest git

2016-08-09 Thread Jens
> https://github.com/gwtproject/gwt/issues/9356 suggests that >value.@Boolean::booleanValue() is rejected but > value@Boolean::booleanValue()() works? > Yes but they are two different things. The first syntax returns the JS function itself (method reference) while the second one executes

Re: working in beta but not in latest git

2016-08-09 Thread Vassilis Virvilis
On Tue, Aug 9, 2016 at 3:15 PM, Jens wrote: > Which alternate syntax? You can either call those methods or don't call > them. > https://github.com/gwtproject/gwt/issues/9356 suggests that value.@Boolean::booleanValue() is rejected but value@Boolean

Re: working in beta but not in latest git

2016-08-09 Thread Jens
Which alternate syntax? You can either call those methods or don't call them. So you would need to wrap your "call the method and lets see if it might fail because its not a Java Boolean" code with try-catch. I think you can just remove the method check when using GWT 2.8. -- J. -- You

Re: working in beta but not in latest git

2016-08-09 Thread Vassilis Virvilis
Ah ha thanks for the pointer. I had read it in the release notes but apparently I forgot it. Trying the alternate syntax gives another error. Looks like the proposed patch is not yet in. Any other ideas how to overcome this syntax? Vassilis On Mon, Aug 8, 2016 at 6:08 PM, Lars

working in beta but not in latest git

2016-08-08 Thread Lars
This is one of the breaking changes JSNI disallows method references to Double, String, Boolean and its super types https://github.com/gwtproject/gwt/issues/9356 See http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0_RC1 -- You received this message because you are subscribed

working in beta but not in latest git

2016-08-08 Thread Vassilis Virvilis
Testing gwt-rc1 (actually latest git) The code is found in gwt-d3 and prevents my project from building. /** * @return true if the value is a Javascript boolean value, a Javascript Boolean object or a Java {@link Boolean} * instance. */ public final native boolean