SQF Syntax: Difference between revisions
m (→Rules) |
m (→Rules) |
||
Line 5: | Line 5: | ||
Binding rules: | Binding rules: | ||
* Curled braces { } group code to '''blocks''' | * Curled braces ({ }) group code to '''blocks''' | ||
* Commands and blocks are followed by '''semicolons''' | * Commands and blocks are followed by '''semicolons''' (;) | ||
The latter rule tells the game engine where one command ends and the next starts. | The latter rule tells the game engine where one command ends and the next starts. |
Revision as of 15:23, 21 December 2006
SQF syntax was introduced in Operation Flashpoint: Resistance and is the common syntax since Armed Assault. An alternative syntax is the SQS syntax (deprecated since Armed Assault).
Rules
Binding rules:
- Curled braces ({ }) group code to blocks
- Commands and blocks are followed by semicolons (;)
The latter rule tells the game engine where one command ends and the next starts.
Example:
Command 1; Command 2; Block { Command 3; Command 4; };
While SQS syntax is line based, SQF syntax is based on structured expressions. End-of-line has no special meaning - it is considered to be equivalent to space or tab, and is therefore not required, even when ending a statement.
Language Constructs
Main language contructs used in functions are:
- if..then..else
- while..do
- since ArmA: for ... from ... to ... step
- since ArmA: switch ... do
- Curled braces { }
- Multiple commands (including assigment commands) are delimited with a semicolon.
Notes
Due to line-based nature of Sqs scripts it is not possible to create multiline string constants in them.
To overcome this limitation you can store multiline in separate SQF function files and load them using loadFile or preprocessFile (the second uses C-like preprocessor with // or /* */ comments and #define macros).