| Summary: | [compiler][null][correlation] unneccesary warning for possible null value - involving non final boolean flag | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | melhor <peter_and1> |
| Component: | Core | Assignee: | Maxime Daniel <maxime_daniel> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | stephan.herrmann |
| Version: | 3.2.1 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Thanks for reporting. This is a known weakness of our current implementation: we do not address variables correlation. Unfortunately, we do not plan to address this in 3.3 time frame. *** This bug has been marked as a duplicate of bug 136309 *** Reopen to assign *** This bug has been marked as a duplicate of bug 136309 *** Removing target since duplicate bug has no target and is not fixed. *** This bug has been marked as a duplicate of bug 538421 *** |
If the warning for 'Null reference' has been enabled in the projects compiler settings, the warning 'The variable xx may be null' occurs in the following code but it shouldn't: boolean isNull = false; String string = anyMethodReturningString(); isNull = (string == null); if (!isNull) { string.toString(); // here the variable value is marked as warning }