Expressions occur in assignment statements or in tests.
Expressions are built of two components: operators and their operands. Most operators are binary, i. e. require two operands. Binary operators occur always between the operands (as in X/Y). Few operators are unary, i. e. require only one operand. A unary operator occurs always before the operand, as in -X.
An expression resolves into a value of a certain type. The resulting type is determined by the types of the values in the expression and the operators in the expression.
When using multiple operands in an expression, the precedence rules of table (12.1) are used.
| Operator | Precedence | Category |
| Not, unary +, unary -, @, ** | Highest (first) | Unary operators, power |
| *, /, div, mod, and, shl, shr, as, <<, >> | Second | Multiplying operators |
| +, -, or, xor, >< | Third | Adding operators |
| =, <>, <, >, <=, >=, in, is | Lowest (Last) | relational operators |
When determining the precedence, the compiler uses the following rules:
Remark The order in which expressions of the same precedence are evaluated is not guaranteed to be left-to-right. In general, no assumptions on which subexpression is evaluated first should be made in such a case.
The compiler will decide which subexpression to evaluate first based on optimization rules. Thus, in the following expression:
f(2) may be executed before g(3). This behavior is distinctly different from Delphi or Turbo Pascal.
If one expression must be executed before the other, it is necessary to split up the statement using temporary results:
A notable exception to this behavior is the evaluation of boolean expressions: if short-circuit boolean evaluation is enabled (the default) then the compiler will evaluate from left to right, but will still respect precedence, i. e. in parts with equal precedence the left operand will always be evaluated before the right one. Thus, the following example:
will evaluate to True, because it is equivalent to