Bug 346904 - ProblemBindingChecker should be conditioned on resolution of includes
Summary: ProblemBindingChecker should be conditioned on resolution of includes
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-codan (show other bugs)
Version: 8.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CDT Codan Inbox CLA
QA Contact: Elena Laskavaia CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-23 16:42 EDT by Sergey Prigogin CLA
Modified: 2013-08-24 22:20 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Prigogin CLA 2011-05-23 16:42:38 EDT 
ProblemBindingChecker should not report unresolved symbols if the file contain at least one unresolved include. It may report unresolved includes instead.
Comment 1 Nathan Ridge CLA 2013-08-24 17:29:05 EDT 
I think this would be too big of a hammer. You can often have situations where only a handful of includes are unresolved in a file (and it's difficult to get them to be resolved - let's say they concern a different platform than the one you are running on) and they cause a few false positive problem bindings, but having other problem bindings reported in the code can still be useful.
Comment 2 Sergey Prigogin CLA 2013-08-24 22:20:18 EDT 
(In reply to comment #1)
The hammer could be made optional. Such behavior of the checker would match the standard behavior of the compiler.