SuperDevMode sometimes puts member fields in __proto__ why is that ?

107 views
Skip to first unread message

stuckagain

unread,
Dec 5, 2014, 5:16:38 AM12/5/14
to google-web-tool...@googlegroups.com
I've been trying out GWT 2.7 and SuperDevMode in combination with the SDBG eclipse plugin.

In the Chrome debugger I noticed that some fields are sometimes available under 'this' but sometimes they are available only in 'this.__proto__'. 
It seems that if I have a boolean field that is set to false that it does not appear in 'this' but under 'this.__proto__' and that I can not see it at all in the SDBG plugin. I filed a bug report on SDBG, but I am trying to figure out how this works in GWT SuperDevMode.

Another thing that takes getting used: list/map structures are not that easy to navigate anymore. I hope they found some way to make it easier to have some support to convert them to something readable in the debugger.


Roberto Lublinerman

unread,
Dec 5, 2014, 10:29:38 AM12/5/14
to google-web-tool...@googlegroups.com

In draft compile Java compile time constants are emitted in the prototype. This should be exactly static final fields of primitive or string type assigned at declaration.

This is the approach to compile time constants taken to implement Java semantics.

FWIW in optimized compiles other fields might be "upgraded" to compile time constants.

--
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-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/d948f131-0da7-4e9a-998a-925e68a62ced%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ray Cromwell

unread,
Dec 5, 2014, 11:49:06 AM12/5/14
to google-web-toolkit-contributors
Static final fields on the prototype? I'm pretty sure these are
promoted to global in optimized mode. Perhaps you meant final
non-static fields? (which we should have an optimization for promoting
to static :) )
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnmswu4mF_7SRPnZjQYjvykkTvgnnthPDfuFy5gpGamcQ%40mail.gmail.com.

Roberto Lublinerman

unread,
Dec 5, 2014, 12:42:10 PM12/5/14
to google-web-tool...@googlegroups.com
Yes,I meant (instance) final fields of primitive or string type initialized at declaration.

Compile time constants are propagated by the compiler in draft and optimized mode.



David

unread,
Dec 6, 2014, 2:21:16 PM12/6/14
to google-web-tool...@googlegroups.com
In my case it is a boolean, but not final, the value does change. Is there an optimisation that removes the field when it is false ?

Reply all
Reply to author
Forward
0 new messages