Preprocessor Defines

Scope of preprocess defines

In general, and for the supplied build setups, preprocessor defines are set globally and across all compilation units.

It is also possible, in some cases, for preprocess defines to be set individually per compilation unit, e.g. to control the exact set of assertions applied when debugging.

Preprocessor defines in the standard 'Debug' build

The standard debug build defines:

• ASSERTIONS_ON
• RANGE_CHECKING

ASSERTIONS_ON enables debug assertions, and can be turned off per compilation unit if extra speed is desired (or turned on per compilation unit in other builds if additional checking is desired).

RANGE_CHECKING turns on point coordinate range checking instrumentation. This define affects the size of certain classes, and it is essential therefore for this to be set consistently across all compilation units in any given build.

Preprocessor defines in the standard 'Release' build

No preprocessor defines are set in the standard release build.