Summary: | [compiler] Null pointer analysis needed in autoboxing/autounboxing | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Luke Hutchison <luke.hutch> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | akiezun, loskutov, mlists, philippe_mulet |
Version: | 3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Luke Hutchison
2005-05-20 01:55:10 EDT
Thanks. Will revisit post 3.1. To be investigated for 3.2 M4 There are two parts to this: a) relate m.get() upon a newly created map to null; b) given an Integer i that may be null, warn on the conditional expression because of the somewhat hidden back and forth boxing conversion. As far as today, none of these is supported by bug 110030. Some of the boxing/unboxing issues are supported though (see NullReferenceTest#test0040 through test0044). Since inter-procedural analysis is not in 3.2 scope, this should be deferred. As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |