[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

6. Configuration Variables

The variable assignments (or settings in libconfig terminology) in a configuration file reside either at the uppermost level (called the Global level) or within a group structure (see section Groups). In the following, configuration variables will be characterized as either being a Global variable, or a Sub-variable of ParentVariable; where ParentVariable is the next parent variable upward in the hierarchy that has a name. The variable ParentVariable can either be a group or a list (see Groups and Lists). Quite often, the immediate parent of a variable assignment is an unnamed group; therefore the ParentVariable of that assignment is the list that contains this unnamed group. For example, the ParentVariable of the variable material_tag in the example in Lists is Materials, since its immediate parent is an unnamed group, but the list structure containing the unnamed group has a name (which is Materials). On the other hand, the variable Materials is a Global variable; since it is assigned at the uppermost level in a configuration file, outside any enclosing structure.

The configuration variable names are case sensitive; meaning that Materials and materials are not the same.

Angora throws an error message for any missing variable or misspelled variable name. This is crucial for ensuring that no optional configuration variable is omitted because of a typo. The valid variable names are read into the Angora source code in compile time from a template file ‘config_all.cfg’. This file, although not required at the time of execution, is distributed with Angora for reference (see Template Configuration File).

[ < ] [ > ]   [ << ] [ Up ] [ >> ]

This document was generated by Ilker Rafet Capoglu on December 12, 2012 using texi2html 1.82.