Deprecation warnings

Tom Rodriguez tom.rodriguez at oracle.com
Wed Feb 1 18:55:57 UTC 2017



Doug Simon wrote:
>> On 1 Feb 2017, at 19:42, Andrew Haley<aph at redhat.com>  wrote:
>>
>> /nfs/zebedee/home/graal/aph/truffle/truffle/com.oracle.truffle.sl/src/com/oracle/truffle/sl/parser/Scanner.java:388: warning: [deprecation] Integer(int) in Integer has been deprecated
>> 		literals.put("return", new Integer(17));
>>
>> There are too many of these.  Shall I just fix them all?
>
> No - we’re stuck with those because these methods are not deprecated on jdk8. So if you use SuppressWarnings, you’ll get a warning on jdk8 about an unnecessary suppression!

Well they can be changed to use valueOf instead, though for test cases I 
think we'll need to make sure we don't actually care about object 
identity.  Those I think we're stuck with.  That's going to be a very 
painful deprecation warning for lots of people.

tom


More information about the graal-dev mailing list