Expressions

In the same way, parentheses (if not used for identifying comments) and braces can be used for structuring of expressions. This means that the expression (1 + 2} * 3 is permitted.

A space after the G address is required only if SMC_ReadNCFile2 would not recognize it as an independent token (example: X abs{-2} instead of Xabs{-2}.).

In contrast with ST, single-position functions do not necessarily have to be called with parentheses (example: sin 3).

When parsing, each partial expression is assigned one of the three types: BOOL, LREAL, or STRING. Accordingly, each Infix operator and each function expects a specific sequence of argument types for which noncompliance (wrong type, too few, or too many arguments) returns an error.

For more information, see: Jump, Using Variables

N01 G36 O$var$ D concat{'prefix_', concat{$var$, '_suffix'}}
N02 G1 X$var$ + sin{pi + 3 * #locvar}
N03 G20 L0 K NOT {myfun{$var$, expt{2, #locvar}} XOR myfun{0, 0}}

It is possible to add your own functions or overwrite an existing implementation. (When parsing the G-code, functions are searched for first in the user functions.)

The SMC_NC_IFunction interface must be implemented and a global instance of the corresponding POU must be transferred to SMC_ReadNCFile2 or SMC_ReadNCFromStream via the structure SMC_NC_GFunctionTable.

The enumeration SMC_GVar_Type is used for the return type and argument types. The entry contained there T_OTHER can be used as a placeholder for a type. When parsing, the system checks that all arguments that correspond to a T_OTHER in the signature have the same type. The type does not matter.

For more information, see: User-Specific G-Code Functions

When possible, the exact position of the defective token and its length are issued in syntax errors. The error position is listed in SMC_ReadNCFile2.errorPos.