This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Incorrect NPE warning | ||
|---|---|---|---|
| Product: | java | Reporter: | Jan Lahoda <jlahoda> |
| Component: | Hints | Assignee: | Jan Lahoda <jlahoda> |
| Status: | VERIFIED FIXED | ||
| Severity: | normal | CC: | everflux, mmirilovic |
| Priority: | P3 | ||
| Version: | 7.3.1 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
*** Bug 228333 has been marked as a duplicate of this bug. *** verified Integrated into 'releases', will be available in build *201305042200* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/ac9ed683ee2c User: Jan Lahoda <jlahoda@netbeans.org> Log: #227954: being more careful about which hypothetical state should be cleared - only those that were introduced by the method's parameter should disappear |
Current trunk builds produce the NPE warning for code like this: ----- class Test { private static void test(@NullAllowed String str) { if (str != null && str.equals("${") && str.equals("{")) { System.err.println(0); } } @interface NullAllowed {} } ----- The warning is on the second str.equals. Thanks to tzezula for the test case.