I think one relevant section might be http://java.sun.com/docs/books/jls/third%5Fedition/html/expressions.html#15.28
Which I got from reading http://stackoverflow.com/questions/1406616/is-java-guaranteed-to-inline-string-constants-if-they-can-be-determined-at-compi But, sounds complicated to be binary compatible but not source compatible ... but, again, I see the merits of the discussion. From: Brian de Alwis <[email protected]> To: E4 Project developer mailing list <[email protected]>, Date: 11/10/2011 11:40 AM Subject: Re: [e4-dev] Suggestion to restructure UIEvents to increase clarity and performance Sent by: [email protected] On 10-Nov-2011, at 10:55 AM, Dean Roberts wrote: > Do we have to be compatible with previously compiled .class files ... I'm assuming the answer is going to be yes here. So it really hinges on: are we guaranteed that all existing compiled classes that referenced the previous version of UIEvents.UIElement.VISIBLE would have had the string inlined? I believe the Java compilers inline static final string references. But I don't know if they *have* to, nor as to whether there are any that don't. Anybody know the applicable part of the JLS? Brian _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
<<inline: graycol.gif>>
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
