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.



On Fri, Dec 5, 2014 at 8:49 AM, 'Ray Cromwell' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> 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 :) )
>
>
> On Fri, Dec 5, 2014 at 7:29 AM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
> > 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.
> >
> > On Dec 5, 2014 2:18 AM, "stuckagain" <david.no...@gmail.com> wrote:
> >>
> >> 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.
> >>
> >>
> >> --
> >> 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-contributors+unsubscr...@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.
> >
> > --
> > 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-contributors+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnmswu4mF_7SRPnZjQYjvykkTvgnnthPDfuFy5gpGamcQ%40mail.gmail.com
> .
> >
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7eTkVStPGXrtfiPk5kO8yr2gyjQCZY4xkAD5ufExWB_6g%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnaifVU5UEa7mU41UuRcEZvwp-NWv_6v5pHsq4Na%3D8uuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to