CP Optimizer file format syntax

This section describes the elements of the CPO file format such as statements, expressions, types, variables, constants or directives, and how to use them.

Introduction and an example
Character encoding
CPO files must be encoded in UTF-8 (or pure ASCII which is a subset of UTF-8).
Comments
Comments in the style of C and C++ can be included in CPO files.
Constants
The CPO file format supports numerical constants such as 123, 2.57, 1.23e+11 or 3.45E-05. There are also several named constants.
Variables
In CPO files, the variables are declared by the following statement:
Identifiers
A variable or expression can be referenced later by the identifier associated with it. As such, the identifier must be unique.
Basic types
Each expression in the CPO file format has an automatically computed type (it is not possible to specify the type of an expression explicitly).
File structure
At the top level, a CPO file is a collection of statements and sections.
Statements
Statements in a CPO file define the problem to be solved (variables, expressions, constraints and so on).
Expressions
Expressions are formed from variables and constants by using operators and functions and by combining expressions together into arrays (array expressions).
Scheduling types
Types designed for describing scheduling problems.
Arrays
The purpose of arrays is to group arguments. For example, the function alldiff does not take a list of integer expressions, it takes an array of them.
More types
This section describes additional types.
Directives
The CPO file format supports two types of directive: #include (to include a file) and #line (to set an additional line number for error reporting).

Parent topic: CP Optimizer File Format Reference Manual