The parser is a work in progress. There are many areas of both C and C++ where the parser has difficulty. For the most part, the parser just skips over the problem areas and keeps parsing. However there are still some open defects that may cause incorrect information to be displayed. See readme.txt for a list of some of the known problems. |
The parser looks for files with certain extensions like .cpp or .h when deciding whether to attempt a parse of the file. The list of extensions that the parser considers to be C/C++ files is defined in the file called CPPExtensions.dat located in the plugins/org.eclipse.cdt.cpp.miners directory. If you find that the parser doesn't seem to be parsing certain files, you should check this file to make sure that your C/C++ file extensions are shown, and add them if not. |
There are 4 ways that a parse can be invoked:
|
The parser needs to know where to look to find include files. By default, only the directory of the file doing the including is searched, so if you want to be able to browse included source in other directories, you will need to set the Parse Include Path. Select menu item Properties from the pop-up menu for your Project in the
C/C++ Projects view. ![]() The Project Properties dialog is opened where you can set the Parse Include Path. ![]() Usability note: After browsing for or typing your include path, you click
|
In some cases, the parser may step into so many files and create so many objects, that the views become hard to navigate. One solution is to filter the views using the drop-down menus. Another option is to explicitly remove the project's parse information (remove objects from the Project Objects view, System Objects view and Parsed Files view.), lower the Parse Quality and reparse the project. To remove a project's parse information, right-click on the project, and choose Parse -> Remove Parse Information from the pop-up menu: ![]() |