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: | smarter "Dereferencing possible null pointer" hint? | ||
---|---|---|---|
Product: | java | Reporter: | athompson <athompson> |
Component: | Hints | Assignee: | Svata Dedic <sdedic> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | athompson |
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
athompson
2013-05-23 17:16:45 UTC
Come to think of it, you would have to rewrite OR logic using NOT ANDs--that is: (A or B) and C --> not(not(A) and not(B)) and C ...so it gets uglier in a hurry. I guess the better approach is to apply either that rule or the OR version of the rule and recursively solve (I think). Okay, it's not as easy as I thought... I guess the simplest approach is to just not bother evaluating anything inside parenthesis (and mixing ANDs and ORs implies parenthesis). Actually, this may be a bug. The code snippet doesn't show an error unless this line is before it: Class<?> valueType = value != null ? value.getClass() : null; ...so I guess that null check is not being overridden by the null check in the IF/ELSE IF chain. This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss Still there but not worth the effort... Reviewing status after bulk issue cleanup. Actually a duplicate of 249320 *** This bug has been marked as a duplicate of bug 249320 *** |