Code vs. Strings: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "<tt>([^ ]*=[^ ]*)<\/tt>" to "{{hl|c= $1}}")
m (Some wiki formatting)
 
Line 1: Line 1:
Since {{arma1}} the convention to use quotation marks for [[String]]s and curly braces for [[Code]] has been formalised. Exceptions, however, do exist. For example [[onMapSingleClick]] and [[onDoubleClick]].<br>
Since {{arma1}} the convention to use quotation marks for [[String]]s and curly braces for [[Code]] has been formalised.
When scripting {{hl|<nowiki>'abc'</nowiki>}}, {{hl|<nowiki>"abc"</nowiki>}} or {{hl|<nowiki>""abc""</nowiki>}} generally indicates data type String, and {{hl|{   }}} indicates data type Code.
Exceptions, however, do exist. For example [[onMapSingleClick]] and [[onDoubleClick]].<br>
When scripting, {{hl|'abc'}} or {{hl|"abc"}} generally indicates a [[String]] data type, and brackets {{hl|{ }<nowiki/>}} indicate [[Code]] data type.


In {{ofp}} many language constructs (including [[forEach]], [[if]], [[while]]) use the concept of "code strings". Code is passed as a string to them and they interpret it as code if they wish. Since version 1.85, string constants can be written in two ways:
In {{ofp}}, many language constructs (including [[forEach]]) use the concept of "code strings".
Code is passed as a string to them and they interpret it as code if they wish. Since version 1.85, code is also accepted.
<sqf>
// {{ofp}} / {{arma1}} only!
"_x setDammage 1" forEach _units;


Using
// from {{ofp}} v1.85+ up to {{arma3}}
*  double quotes:  {{hl|"Hello"}}
{ _x setDamage 1 } forEach _units;
or
</sqf>
* curled braces {{hl|c= {a=a+1}}}


A partial list of commands which expect code as parameter is provided at [[Code Commands]].


== Code Commands ==
== Code Commands ==
'''Code commands''' are any commands from the scripting language expecting a coded statement string as one of their parameters. Earlier engines accepted code as such when it was provided as a [[String]] using quotation marks, ''or'' using braces. Since Armed Assault the engine '''specifically''' requires braces. Thus, because the way the engine determines whether it is dealing with code has changed, this list is presented here.
 
'''Code commands''' are any commands from the scripting language expecting a coded statement string as one of their parameters.
Earlier engines accepted code as such when it was provided as a [[String]] using quotation marks, ''or'' using braces.
Since {{arma1}} the engine '''specifically''' requires braces.
Thus, because the way the engine determines whether it is dealing with code has changed, this list is presented here.


Commands passed as data type [[Code]]: Last updated: {{GVI|arma3|2.02}}
Commands passed as data type [[Code]]: Last updated: {{GVI|arma3|2.02}}
{{Columns|3|
{{Columns|3|
* [[&&]]
* [[&&]]
* [[a or b|||]]
* [[a or b|<nowiki/>||]]
* [[addPublicVariableEventHandler]]
* [[addPublicVariableEventHandler]]
* [[and]]
* [[and]]
Line 64: Line 71:
* [[with]]
* [[with]]
}}
}}


== String Commands ==
== String Commands ==
Commands passed as data type [[String]]:
Commands passed as data type [[String]]:
* map [[onDoubleClick]] "[[Code]]"
* map [[onDoubleClick]] "[[Code]]"

Latest revision as of 15:52, 14 November 2023

Since Armed Assault the convention to use quotation marks for Strings and curly braces for Code has been formalised. Exceptions, however, do exist. For example onMapSingleClick and onDoubleClick.
When scripting, 'abc' or "abc" generally indicates a String data type, and brackets { } indicate Code data type.

In Operation Flashpoint, many language constructs (including forEach) use the concept of "code strings". Code is passed as a string to them and they interpret it as code if they wish. Since version 1.85, code is also accepted.

// Operation Flashpoint / Armed Assault only! "_x setDammage 1" forEach _units; // from Operation Flashpoint v1.85+ up to Arma 3 { _x setDamage 1 } forEach _units;


Code Commands

Code commands are any commands from the scripting language expecting a coded statement string as one of their parameters. Earlier engines accepted code as such when it was provided as a String using quotation marks, or using braces. Since Armed Assault the engine specifically requires braces. Thus, because the way the engine determines whether it is dealing with code has changed, this list is presented here.

Commands passed as data type Code: Last updated: Arma 3 logo black.png2.02


String Commands

Commands passed as data type String: