http://gwt-code-reviews.appspot.com/1513803/diff/1/dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter.java
File dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter.java (right):
http://gwt-code-reviews.appspot.com/1513803/diff/1/dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter.java#newcode864
dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter.java:864: }
On 2011/08/05 21:19:37, stephenh wrote:
Besides fixing up strings, a class literal could end up with it's
super class
literal being in a different fragment. (If you want details of how
this can
happen, I have a reproduction.)
E.g. foo_2_classLit = createForClass("package", "name", Bar.class);
Would fail if bar_2_classLit ended up in a separate fragment.
This uses the same fixup logic as used else where to pull out
Bar.class and move
it to leftovers if it's not in our fragment or not already there.
Did you try this against trunk or GWT 2.3/2.4? I made some changes
recently to the way liveness of class literals are calculated that may
or may not have an effect relative to this. Do you have the repo code?
http://gwt-code-reviews.appspot.com/1513803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
