| Summary: | [compiler][null][pattern] asymetry for potential nulls involving && | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jeremy <eclipse.user> |
| Component: | Core | Assignee: | Ayushman Jain <amj87.iitr> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | P5 | ||
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | stalebug | ||
|
Description
Jeremy
As far as fields are concerned, we currently have no plans to support them. Reproduced with 3.3 for i an j swap between choose and equivalentChoose, will investigate. Updated the summary to reflect the case I'll tackle. Added test cases NullReferenceTest#86 and 87. We do not handle variables correlation so far. Accordingly, the spurious warning in equivalentChoose is incorrect but expected. The no warning in choose comes from the fact that another limitation strikes: we do not see j as tainted, because our encoding of null status makes no difference between tainted and potential null. The net result is that: - the observed misbehavior will be fixed if we decide at some point in time to invest in specific variables correlation patterns (variables correlation in general is out of scope); I'll tag the bug accordingly; - I won't spend more time to align the 'good behavior' to the same misbehavior for the sole sake of consistency; if at a future time we decide to recode, then the misbehavior will probably show up, with the same treatment as the other one (i.e., treat with pattern if decided so). Changing OS from Mac OS to Mac OS X as per bug 185991 This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |