5.6.9.2 Simple Data Operators

Note

This section describes the implementation of MS-VBAL §5.6.9.2 Simple Data Operators.

Runtime Semantics

The evaluation pipeline of all operators follows a fixed sequence of three steps:

Effective type. The effective type of the operation is determined, based on the declared type of its operands.
Validation. All non-null operands (every operand that is not a VBNullValue) are let-coerced to the determined effective type of the operation (RD-VBAL §5.5.1.2 Runtime semantics).
Evaluation. A templated method evaluates a result from the validated operands.

The sequence may be aborted at any point to return an error result. An error result encapsulates VBRuntimeErrorInfo error metadata.

Operand validation

The arithmetic, relational and concatenation (&) operators validate their operands through OperatorRuntimeSemantics.LetCoerceNonNullOperand.

LetCoerceNonNullOperand has a TypeInfo-equality short-circuit: an operand whose TypeInfo equals the destination type is not coerced. The short-circuit does not apply to a VBVariantValue operand: a Variant operand is always let-coerced, even when its TypeInfo equals the destination type.

A VBVariantValue's TypeInfo mirrors its wrapped value's; see RD-VBAL §5.5.1.2.12 Let-coercion to Variant.

Computation in the effective type

The evaluation step (step 3) computes an operator's result in the operation's effective type, in that type's own representation, and never through a Double intermediate.

Effective type	Computed in
`Long`	The `Long` representation, a 32-bit `int`.
`Currency`, `Decimal`	`decimal`
`Single`	`float`

See RD-VBAL §5.6.9.3 Arithmetic Operators for checked arithmetic and the ^ operator, RD-VBAL §5.6.9.5 Relational Operators for comparisons, and RD-VBAL §5.6.9.8 Logical Operators for bitwise computation.

Implementation

The node parameter of OperatorRuntimeSemantics<TContext,TFlags> is typed ExpressionNode.
Nothing in the operator runtime-semantics hierarchy reads .Left, .Right or .Token off the node parameter. It reads the node's identity (.Identity) and its source location, to attribute the operation and its errors to the node. Beyond those, it only tests the node's type: to flag which operand position (unary, binary left or binary right) an operand holds in the semantic analysis, and to name the node type in an internal-error message.
Only the token-dispatch layer, OperatorRuntimeSemanticsProvider, reads .Token off the operator node.

The operator strategies do not require a binary or unary operator node (VBBinaryOperatorExpressionNode, VBUnaryOperatorExpressionNode) as their node parameter. Requiring one would force the fabrication of synthetic nodes, which RD-VBA rules out, as it does for let-coercion (RD-VBAL §5.5.1.2 Runtime semantics).

See RD-VBAL §5.4.2.10 Select Case Statement for a caller that invokes the operator strategies directly, with its own expression node.