Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346904

Summary:	ProblemBindingChecker should be conditioned on resolution of includes
Product:	[Tools] CDT	Reporter:	Sergey Prigogin <eclipse.sprigogin>
Component:	cdt-codan	Assignee:	CDT Codan Inbox <cdt-codan-inbox>
Status:	NEW ---	QA Contact:	Elena Laskavaia <elaskavaia.cdt>
Severity:	normal
Priority:	P3	CC:	cdtdoug, yevshif, zeratul976
Version:	8.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Sergey Prigogin

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

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

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.