TranslationConfiguration

Builds a TranslationConfiguration.

If true the (cpp) frontend connects a node to required includes.

should the code of a node be shown as parameter in the node *

This is the data structure for storing the compilation database. It stores a mapping from the File to the list of files that have to be included to their path, specified by the parameter in the compilation database. This is currently only used by the CXXLanguageFrontend.

Set to true to generate debug output for the parser.

Switch off cleaning up TypeManager memory after analysis.

Should parser/translation fail on parse/resolving errors (true) or try to continue in a best-effort manner (false).

This acts as a block list for include files, if the array is not empty. The specified include files will be excluded from being parsed and processed in the CPG. The blocklist entries always take priority over those in the whitelist.

Paths to look for include files.

This acts as a white list for include files, if the array is not empty. Only the specified includes files will be parsed and processed in the CPG, unless it is a port of the blacklist, in which it will be ignored.

This sub configuration object holds all information about inference and smart-guessing.

This list contains all languages which we want to translate.

Set to true to transitively load include files into the CPG.

If true the frontend shall use a heuristic matching of comments found in the source file to match them to the closest AST node and save it in the comment property.

Set to true to process annotations or annotation-like elements.

Source code files to parse.

Returns a list of all analyzed files.

Definition of additional symbols, mostly useful for C++.

If false, the type listener system is only activated once the frontends are done building the initial AST structure. This avoids errors where the type of a node may depend on the order in which the source files have been parsed.

If true, the ASTs for the source files are parsed in parallel, but the passes afterwards will still run in a single thread. This speeds up initial parsing but makes sure that further graph enrichment algorithms remain correct.

Only relevant for C++. A unity build refers to a build that consolidates all translation units into a single one, which has the advantage that header files are only processed once, adding far less duplicate nodes to the graph