## Options Tab

The Options tab in the Project Configuration dialog (which you open with Project->Configure) provides a variety of analysis options, including information about the source code, how to handle errors found during parsing, and items to count for complexity metrics.

The Options tab contains the following fields:

- Prompt if errors occurred in Order Parsing Phase
  By default, you are prompted for how to handle errors that occur when determining the order in which files should be analyzed. When prompted, you may choose to ignore that error or all future errors. Turn this option off to disable this prompting feature. If you turned it off during analysis, but later want to turn error prompting back on, check it here.
- Prompt on a File Parse error
  By default, you are prompted for how to handle errors that occur when analyzing files. When prompted, you may choose to ignore that error or all future errors. Turn this option off to disable this prompting feature. If you turned it off during analysis, but later want to turn error prompting back on, check it here.
- Count For-Loops in Complexity
  Remove the check from this box if you do not want FOR-loops considered when calculating the complexity metrics shown in the Information Browser and the Program Unit Complexity report. Complexity measures the number of independent paths through a program unit.
- Count And/Or Operators in Strict Complexity
  Place a checkmark in this box if you also want “and” and “or” operators considered when calculating the strict complexity metric shown in the Program Unit Complexity report. Strict complexity is like cyclomatic complexity, except that each short-circuit operator (“and then” and “or else”) adds 1 to the complexity.
- Count Exception Handlers in Complexity
  Place a checkmark in this box if you also want exception handlers considered when calculating the complexity metrics shown in the Information Browser and the Program Unit Complexity report.
- Create relations between formal and actual parameters
  Place a checkmark in this box if you want the analysis to create relations between formal and actual parameters. The actual parameters linked to formal parameters include items used in expressions passed as actual parameters. This option is off by default to speed up analysis.
- Instantiate Generic Bodies
  This option is disabled as of this document’s publication date. By default, only generic specs are instantiated. This feature would create a copy of the generic body as well, with actual parameters substituted for formal parameters where appropriate. However, this adds significant time to the analysis process.
- Optimize for less memory usage versus speed
  Place a checkmark in this box if you want to use Understand for Ada in a very low memory consumption mode. In order to conserve memory, Understand for Ada frees memory used to process a program unit if that program unit is not needed. Using this option may slow down operation significantly. It is off by default.
- Associate Comments
  You can choose which source code comments should be associated with an entity. Your choice depends on how you typically comment entity definitions. The choices are “never” (comments are not associated with entities), “comments before definitions,” “comments after definitions” (the default), and “longest comment before or definition.”

Scientific Toolworks, Inc. http://www.scitools.com