PDOM

When the PDOM is created for a project, it constructs a Database object to manage its low-level storage.

I've added the PDOM classes, and considering the size of the application, Bare Bones just doesn't seem appropriate anymore.

Nevertheless, it does build a very important object for the project called a PDOM.

There, you'll see a *. pdom file for each of your projects.

Then, it stores a reference to the unit's file in the PDOM, along with references to the included directives and macro definitions.

This provides the routines that store the indexer's data within the PDOM.

The constructors for these new objects access the PDOM to store their information.

To show how this works, I need to back up and explain how the PDOM operates.

After the indexer receives the IASTTranslationUnit, it gets a write lock on the PDOM and begins persisting the TranslationUnit's data.

In Part 5, I discuss code completion and content assist, including how they work and how they access the PDOM index.

You can also search through the PDOM using the static methods provided in the DOMSearchUtil class.

To activate it, I updated the previous ASTAction to visit elements in the AST and the PDOM's storage. (See Download for the code. )