Community
Participate
Working Groups
Hello, The parser contains a lot of logic, usually in classes, which tend to be very usable in Codan checkers. Examples include classes such as: org.eclipse.cdt.internal.core.dom.parser.cpp.semantics.SemanticUtil org.eclipse.cdt.internal.core.dom.parser.cpp.ClassTypeHelper These classes are tested to correctly implement the logic described in the C++ standard and are updated alongside with it. Hence, especially since Codan is an integral part of CDT now, I believe that Codan would benefit from being provided access to org.eclipse.cdt.internal.core.dom.parser packages, in order to avoid the obvious downsides of having to duplicate the semantics provided there. Note that if one day a need arises to change the logic in the parser (such as updates to the C++ standard), the exactly same reason will make it necessary to update the Codan checkers - so introducing this dependency into code looks very natural.
Created attachment 201649 [details] Proposed change
Wouldn't it be a better idea to expose the logic that is useful to codan in public APIs in core? I began doing that with org.eclipse.cdt.core.dom.ast.cpp.SemanticQueries.
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.