SQF Syntax - Revision history

Lou Montana: Fix example

2024-04-24T15:51:27Z

Fix example

← Older revision		Revision as of 17:51, 24 April 2024
Line 94:		Line 94:

	// create a new unit in the player group		// create a new unit in the player group
	group player createUnit ["B_RangeMaster_F", getPosATL player, [], 0, "~~FORM~~"];		group player createUnit ["B_RangeMaster_F", getPosATL player, [], 0, "NONE"];

	// output the Array size again		// output the Array size again

Lou Montana: Fix semicolon

2023-11-02T13:59:47Z

Fix semicolon

Lou Montana: Text replacement - "\{\{ Wikipedia \| ([-(){}a-zA-Z0-9_#':%\/\\]+) \| ([-(){}a-zA-Z0-9_#':%\/\\ ]+) \}\}" to "{{Link|https://en.wikipedia.org/wiki/$1|$2}}"

2023-02-23T23:50:06Z

Text replacement - "\{\{ *Wikipedia *\| *([-(){}a-zA-Z0-9_#':%\/\\]+) *\| *([-(){}a-zA-Z0-9_#':%\/\\ ]+) *\}\}" to "{{Link|https://en.wikipedia.org/wiki/$1|$2}}"

← Older revision		Revision as of 01:50, 24 February 2023
Line 5:		Line 5:
	<small>		<small>
	* "Status Quo" was a code name for {{Link\|https://en.wikipedia.org/wiki/Operation_Flashpoint\|Operation Flashpoint}}		* "Status Quo" was a code name for {{Link\|https://en.wikipedia.org/wiki/Operation_Flashpoint\|Operation Flashpoint}}
	* "Combined Arms" was a code name for {{~~Wikipedia~~\|ARMA_(series)\|{{arma}}}}		* "Combined Arms" was a code name for {{Link\|https://en.wikipedia.org/wiki/ARMA_(series)\|{{arma}}}}
	* "Futura" was a code name for {{~~Wikipedia~~\|ARMA_3\|{{arma3}}}}.		* "Futura" was a code name for {{Link\|https://en.wikipedia.org/wiki/ARMA_3\|{{arma3}}}}.
	</small>		</small>

Lou Montana: Text replacement - "Link\|https:\/\/en\.wikipedia\.org\/([^w][^i])" to "Link|https://en.wikipedia.org/wiki/$1"

2023-02-23T21:11:04Z

Text replacement - "Link\|https:\/\/en\.wikipedia\.org\/([^w][^i])" to "Link|https://en.wikipedia.org/wiki/$1"

← Older revision		Revision as of 23:11, 23 February 2023
Line 4:		Line 4:

	<small>		<small>
	* "Status Quo" was a code name for {{Link\|https://en.wikipedia.org/Operation_Flashpoint\|Operation Flashpoint}}		* "Status Quo" was a code name for {{Link\|https://en.wikipedia.org/wiki/Operation_Flashpoint\|Operation Flashpoint}}
	* "Combined Arms" was a code name for {{Wikipedia\|ARMA_(series)\|{{arma}}}}		* "Combined Arms" was a code name for {{Wikipedia\|ARMA_(series)\|{{arma}}}}
	* "Futura" was a code name for {{Wikipedia\|ARMA_3\|{{arma3}}}}.		* "Futura" was a code name for {{Wikipedia\|ARMA_3\|{{arma3}}}}.

Lou Montana: Text replacement - "\{\{Wikipedia \| ([a-zA-Z0-9_#]+) \| ([a-zA-Z0-9_ #]+) *\}\}" to "{{Link|https://en.wikipedia.org/$1|$2}}"

2023-02-23T21:02:29Z

Text replacement - "\{\{Wikipedia *\| *([a-zA-Z0-9_#]+) *\| *([a-zA-Z0-9_ #]+) *\}\}" to "{{Link|https://en.wikipedia.org/$1|$2}}"

← Older revision		Revision as of 23:02, 23 February 2023
Line 4:		Line 4:

	<small>		<small>
	* "Status Quo" was a code name for {{~~Wikipedia~~\|Operation_Flashpoint\|Operation Flashpoint}}		* "Status Quo" was a code name for {{Link\|https://en.wikipedia.org/Operation_Flashpoint\|Operation Flashpoint}}
	* "Combined Arms" was a code name for {{Wikipedia\|ARMA_(series)\|{{arma}}}}		* "Combined Arms" was a code name for {{Wikipedia\|ARMA_(series)\|{{arma}}}}
	* "Futura" was a code name for {{Wikipedia\|ARMA_3\|{{arma3}}}}.		* "Futura" was a code name for {{Wikipedia\|ARMA_3\|{{arma3}}}}.

Lou Montana: Text replacement - "{{HashLink" to "{{Link"

2023-01-04T16:43:59Z

Text replacement - "{{HashLink" to "{{Link"

← Older revision		Revision as of 18:43, 4 January 2023
Line 147:		Line 147:
	== Binary Operators ==		== Binary Operators ==

	Binary [[:Category:Scripting_Commands_Arma_3\|operators]] expect two arguments ({{hl\|<1st argument> binary <2nd argument>}}) and are executed according to their {{~~HashLink~~\|#precedence}}. If their precedence is equal, they are executed left to right.		Binary [[:Category:Scripting_Commands_Arma_3\|operators]] expect two arguments ({{hl\|<1st argument> binary <2nd argument>}}) and are executed according to their {{Link\|#precedence}}. If their precedence is equal, they are executed left to right.

	As example, we will look into the following expression:		As example, we will look into the following expression:

Lou Montana: Some wiki formatting

2022-07-25T12:16:19Z

Some wiki formatting

← Older revision		Revision as of 14:16, 25 July 2022
Line 19:		Line 19:
	== Terminating an expression ==		== Terminating an expression ==

	An SQF expression has to be terminated via either ~~{{ic\|~~;}} (preferred by convention!) or ~~{{ic\|~~,}}.		An SQF expression has to be terminated via either <sqf inline>;</sqf> (preferred by convention!) or <sqf inline>,</sqf>.

	<sqf>		<sqf>
Line 26:		Line 26:
	</sqf>		</sqf>
	In the above example, there are three expressions:		In the above example, there are three expressions:
	# ~~{{ic\|~~_num {{=}} 10}}		# <sqf inline>_num = 10</sqf>
	# ~~{{ic\|~~_num {{=}} _num + 20}}		# <sqf inline>_num = _num + 20</sqf>
	# ~~{{ic\|[[~~systemChat~~]] [[~~str]] _num}}		# <sqf inline>systemChat str _num</sqf>
	All are separated by ~~{{hl\|~~;}} and not the line return - they could all be inlined and it would not impact the code.		All are separated by <sqf inline>;</sqf> and not the line return - they could all be inlined and it would not impact the code.


	== Brackets ==		== Brackets ==

	* ~~{{ic\|~~()}} - Round brackets are used to override the default [[Order of Precedence]] or improve legibility.		* <sqf inline>()</sqf> - Round brackets are used to override the default [[Order of Precedence]] or improve legibility.
	* ~~{{ic\|~~[]}} - Square brackets define [[Array]]s.		* <sqf inline>[]</sqf> - Square brackets define [[Array]]s.
	* ~~{{ic\|~~<~~nowiki~~>{}</~~nowiki~~>}} - Curly brackets enclose instances of the [[Code]] [[:Category:Data Types\|Data Type]]. They are also used in [[Control Structures]].		* <sqf inline>{}</sqf> - Curly brackets enclose instances of the [[Code]] [[:Category:Data Types\|Data Type]]. They are also used in [[Control Structures]].


Line 75:		Line 75:
	It should be mentioned that there is a [[comment]] unary [[:Category:Scripting_Commands_Arma_3\|operator]] that should not be used as it will actually be executed (thus taking time to execute) but does nothing besides consuming a [[String\|string]].		It should be mentioned that there is a [[comment]] unary [[:Category:Scripting_Commands_Arma_3\|operator]] that should not be used as it will actually be executed (thus taking time to execute) but does nothing besides consuming a [[String\|string]].
	There is no benefit in using it and the reason it exists is solely for backward compatibility.		There is no benefit in using it and the reason it exists is solely for backward compatibility.
	Another way to make a ''comment'' that way, is to just place a [[String\|string]]: ~~{{ic\|[...]~~; "i can be considered as a comment but should not be used"; ~~[...]}}~~		Another way to make a ''comment'' that way, is to just place a [[String\|string]]: <sqf inline>/* some code /; "i can be considered as a comment but should not be used"; / some other code */</sqf>

	''Comments are removed during the [[PreProcessor_Commands\|preprocessing]] phase.'' This is important to know as that prevents usage in e.g a [[String\|string]] that gets compiled using the [[compile]] unary [[:Category:Scripting Commands\|operator]] or when only using [[loadFile]].		''Comments are removed during the [[PreProcessor_Commands\|preprocessing]] phase.'' This is important to know as that prevents usage in e.g a [[String\|string]] that gets compiled using the [[compile]] unary [[:Category:Scripting Commands\|operator]] or when only using [[loadFile]].
Line 108:		Line 108:
	System: 6		System: 6

	As you can see, ~~{{ic\|~~_unitsArray}} was not automatically updated as it would have been if it was not generated each time. If [[allUnits]] was just a [[Variables\|global variable]] with a reference to some internal managed array, our private [[Variables\|variable]] should have had reflected the change as [[Data_Types\|value types]] are passed by reference.		As you can see, <sqf inline>_unitsArray</sqf> was not automatically updated as it would have been if it was not generated each time. If [[allUnits]] was just a [[Variables\|global variable]] with a reference to some internal managed array, our private [[Variables\|variable]] should have had reflected the change as [[Data_Types\|value types]] are passed by reference.
	The reason for this is because [[allUnits]] and other nular{{sic}} operators just return the current state of something and do not return a reference to eg. an [[Array\|array]] containing all units.		The reason for this is because [[allUnits]] and other nular{{sic}} operators just return the current state of something and do not return a reference to eg. an [[Array\|array]] containing all units.
	It is generated each time, which is why some of theese operators are more expensive to run then ''just'' using a [[Variables\|variable]].		It is generated each time, which is why some of theese operators are more expensive to run then ''just'' using a [[Variables\|variable]].
Line 115:		Line 115:
	== Unary Operators ==		== Unary Operators ==

	The unary [[:Category:Scripting_Commands_Arma_3\|operators]] are [[:Category:Scripting_Commands_Arma_3\|operators]] that expect an argument on their right side ({{ic\|unary <argument>}}). They always will take the first argument that occurs.		The unary [[:Category:Scripting_Commands_Arma_3\|operators]] are [[:Category:Scripting_Commands_Arma_3\|operators]] that expect an argument on their right side ({{hl\|unary <argument>}}). They always will take the first argument that occurs.

	A common mistake would be the following:		A common mistake would be the following:
Line 134:		Line 134:
	The ''3'' then is passed to [[select]] which does not knows what to do with a number as left argument and thus errors out.		The ''3'' then is passed to [[select]] which does not knows what to do with a number as left argument and thus errors out.

	To do it correctly, one would have to put the ~~{{ic\|~~_arr select 2}} in brackets.		To do it correctly, one would have to put the <sqf inline>_arr select 2</sqf> in brackets.
	The correct code thus would be:		The correct code thus would be:
	<sqf>		<sqf>
Line 147:		Line 147:
	== Binary Operators ==		== Binary Operators ==

	Binary [[:Category:Scripting_Commands_Arma_3\|operators]] expect two arguments ({{ic\|<1st argument> binary <2nd argument>}}) and are executed according to their {{HashLink\|#precedence}}. If their precedence is equal, they are executed left to right.		Binary [[:Category:Scripting_Commands_Arma_3\|operators]] expect two arguments ({{hl\|<1st argument> binary <2nd argument>}}) and are executed according to their {{HashLink\|#precedence}}. If their precedence is equal, they are executed left to right.

	As example, we will look into the following expression:		As example, we will look into the following expression:

Lou Montana: Some wiki formatting

2022-04-05T15:39:28Z

Some wiki formatting

← Older revision		Revision as of 17:39, 5 April 2022
Line 21:		Line 21:
	An SQF expression has to be terminated via either {{ic\|;}} (preferred by convention!) or {{ic\|,}}.		An SQF expression has to be terminated via either {{ic\|;}} (preferred by convention!) or {{ic\|,}}.

	_num = 10;		<sqf>
	_num = _num + 20; [[systemChat~~]] [[~~str]] _num;		_num = 10;
			_num = _num + 20; systemChat str _num;
			</sqf>
	In the above example, there are three expressions:		In the above example, there are three expressions:
	# {{ic\|_num {{=}} 10}}		# {{ic\|_num {{=}} 10}}
Line 61:		Line 63:
	In SQF, there are two kind of comments:		In SQF, there are two kind of comments:
	<sqf>		<sqf>
	// In-line comment that ends on new line		// in-line comment that ends on new line

	/* ~~Block Comment~~ that can span above multiple lines		/* block comment that can span above multiple lines
	and ends on the following character combination: */		and ends on the following character combination: */
	</sqf>		</sqf>

	A comment can occur anywhere but inside a [[String\|string]].		A comment can occur anywhere but inside a [[String\|string]].
	For example, the following would be valid:		For example, the following would be valid:
	<sqf>1 + /* ~~Some~~ random comment in an expression. */ 1</sqf>		<sqf>1 + /* some random comment in an expression */ 1</sqf>

	It should be mentioned that there is a [[comment]] unary [[:Category:Scripting_Commands_Arma_3\|operator]] that should not be used as it will actually be executed (thus taking time to execute) but does nothing besides consuming a [[String\|string]].		It should be mentioned that there is a [[comment]] unary [[:Category:Scripting_Commands_Arma_3\|operator]] that should not be used as it will actually be executed (thus taking time to execute) but does nothing besides consuming a [[String\|string]].
Line 84:		Line 87:
	Consider following example in a mission with e.g. 5 units:		Consider following example in a mission with e.g. 5 units:
	<sqf>		<sqf>
	// ~~Put~~ the result of allUnits into a Variable		// put the result of allUnits into a Variable
	_unitsArray = allUnits;		_unitsArray = allUnits;

	// ~~Display~~ the current Array size using systemChat		// display the current Array size using systemChat
	systemChat str count _unitsArray;		systemChat str count _unitsArray;

	// ~~Create~~ a new unit in the player group		// create a new unit in the player group
	group player createUnit ["B_RangeMaster_F", getPosATL player, [], 0, "FORM"];		group player createUnit ["B_RangeMaster_F", getPosATL player, [], 0, "FORM"];

	// ~~Output~~ the Array size again		// output the Array size again
	systemChat str count _unitsArray;		systemChat str count _unitsArray;

	// ~~Output~~ the size of allUnits		// output the size of allUnits
	systemChat str count allUnits;		systemChat str count allUnits;
	</sqf>		</sqf>
Line 116:		Line 119:
	A common mistake would be the following:		A common mistake would be the following:
	<sqf>		<sqf>
	// ~~Create~~ some Array containing three arrays		// create some Array containing three arrays
	_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];		_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];

	// ~~Wrongly~~ use the select operator to get the count of the third array		// wrongly use the select operator to get the count of the third array
	count _arr select 2; // ~~Error~~		count _arr select 2; // error
	</sqf>		</sqf>

Line 126:		Line 129:

	Let's put some brackets in the right places to make the mistake understandable:		Let's put some brackets in the right places to make the mistake understandable:
	<sqf>(count _arr) select 2; // ~~Error~~</sqf>		<sqf>(count _arr) select 2; // error</sqf>

	Due to the nature of unary [[:Category:Scripting_Commands_Arma_3\|operators]], count instantly consumes our [[Variables\|variable]] ''_arr'' and returns the number ''3''.		Due to the nature of unary [[:Category:Scripting_Commands_Arma_3\|operators]], count instantly consumes our [[Variables\|variable]] ''_arr'' and returns the number ''3''.
Line 134:		Line 137:
	The correct code thus would be:		The correct code thus would be:
	<sqf>		<sqf>
	// ~~Create~~ an ~~Array~~ containing three Arrays		// create an array containing three Arrays
	_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];		_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];

	// ~~Use Brackets~~ to correctly get count of the third Array		// use brackets to correctly get count of the third Array
	count (_arr select 2); // ~~Good~~ :) will evaluate to 2		count (_arr select 2); // good :) will evaluate to 2
	</sqf>		</sqf>

Line 148:		Line 151:
	As example, we will look into the following expression:		As example, we will look into the following expression:
	<sqf>		<sqf>
	// ~~Create~~ a nested Array with 5 levels		// create a nested Array with 5 levels
	_arr = [[[[[1]]]]];		_arr = [[[[[1]]]]];

	// ~~Receive~~ the nested number with some random math expressions		// receive the nested number with some random math expressions
	_arr select 0 select 1 - 1 select 15 / 3 - 5 select 0 select 10 * 10 + 4 * 0 - 100 // ~~Evaluates~~ to 1.		_arr select 0 select 1 - 1 select 15 / 3 - 5 select 0 select 10 * 10 + 4 * 0 - 100 // evaluates to 1
	</sqf>		</sqf>

Lou Montana: Some wiki formatting

2022-04-05T15:36:42Z

Some wiki formatting

← Older revision		Revision as of 17:36, 5 April 2022
Line 84:		Line 84:
	Consider following example in a mission with e.g. 5 units:		Consider following example in a mission with e.g. 5 units:
	<sqf>		<sqf>
	// Put the result of allUnits into a ~~Variables\|variable.~~		// Put the result of allUnits into a Variable
	_unitsArray = allUnits;		_unitsArray = allUnits;

	// Display the current Array size using systemChat.		// Display the current Array size using systemChat
	systemChat str count _unitsArray;		systemChat str count _unitsArray;

	// Create a new unit in the player group.		// Create a new unit in the player group
	group player createUnit ["B_RangeMaster_F", getPosATL player, [], 0, "FORM"];		group player createUnit ["B_RangeMaster_F", getPosATL player, [], 0, "FORM"];

Line 116:		Line 116:
	A common mistake would be the following:		A common mistake would be the following:
	<sqf>		<sqf>
	// Create some Array containing three arrays.		// Create some Array containing three arrays
	_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];		_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];

	// Wrongly use the select operator to get the count of the third array.		// Wrongly use the select operator to get the count of the third array
	count _arr select 2; // Error		count _arr select 2; // Error
	</sqf>		</sqf>
Line 134:		Line 134:
	The correct code thus would be:		The correct code thus would be:
	<sqf>		<sqf>
	// Create an Array containing three Arrays.		// Create an Array containing three Arrays
	_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];		_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];

Line 148:		Line 148:
	As example, we will look into the following expression:		As example, we will look into the following expression:
	<sqf>		<sqf>
	// Create a nested Array with 5 levels.		// Create a nested Array with 5 levels
	_arr = [[[[[1]]]]];		_arr = [[[[[1]]]]];

	// Receive the nested number with some random math expressions.		// Receive the nested number with some random math expressions
	_arr select 0 select 1 - 1 select 15 / 3 - 5 select 0 select 10 * 10 + 4 * 0 - 100 // Evaluates to 1.		_arr select 0 select 1 - 1 select 15 / 3 - 5 select 0 select 10 * 10 + 4 * 0 - 100 // Evaluates to 1.
	</sqf>		</sqf>

Lou Montana: Some wiki formatting

2022-04-05T15:35:31Z

Some wiki formatting

← Older revision		Revision as of 17:35, 5 April 2022
Line 60:		Line 60:

	In SQF, there are two kind of comments:		In SQF, there are two kind of comments:
	~~{{cc\|~~In-line comment that ends on new line}}		<sqf>
			// In-line comment that ends on new line
	~~{{codecomment\|~~/* Block Comment that can span above multiple lines
	and ends on the following character combination: */}}		/* Block Comment that can span above multiple lines
			and ends on the following character combination: */
			</sqf>
	A comment can occur anywhere but inside a [[String\|string]].		A comment can occur anywhere but inside a [[String\|string]].
	For example, the following would be valid:		For example, the following would be valid:
	1 + ~~{{codecomment\|~~/* Some random comment in an expression. */}} 1		<sqf>1 + /* Some random comment in an expression. */ 1</sqf>

	It should be mentioned that there is a [[comment]] unary [[:Category:Scripting_Commands_Arma_3\|operator]] that should not be used as it will actually be executed (thus taking time to execute) but does nothing besides consuming a [[String\|string]].		It should be mentioned that there is a [[comment]] unary [[:Category:Scripting_Commands_Arma_3\|operator]] that should not be used as it will actually be executed (thus taking time to execute) but does nothing besides consuming a [[String\|string]].
Line 81:		Line 83:

	Consider following example in a mission with e.g. 5 units:		Consider following example in a mission with e.g. 5 units:
	~~{{cc\|~~Put the result of [[allUnits]] into a [[Variables\|variable]].}}		<sqf>
	_unitsArray = [[allUnits]];		// Put the result of allUnits into a Variables\|variable.
			_unitsArray = allUnits;
	~~{{cc\|~~Display the current [[Array~~\|array]]~~ size using [[systemChat]].}}
	[[systemChat~~]] [[~~str~~]] [[~~count]] _unitsArray;		// Display the current Array size using systemChat.
			systemChat str count _unitsArray;
	~~{{cc\|~~Create a new unit in the player group.}}
	[[group~~]] [[~~player~~]] [[~~createUnit]] ["B_RangeMaster_F", ~~[[position]] [[~~player]], [], 0, "FORM"];		// Create a new unit in the player group.
			group player createUnit ["B_RangeMaster_F", getPosATL player, [], 0, "FORM"];
	~~{{cc\|~~Output the [[Array~~\|array]]~~ size again}}
	[[systemChat~~]] [[~~str~~]] [[~~count]] _unitsArray;		// Output the Array size again
			systemChat str count _unitsArray;
	~~{{cc\|~~Output the size of [[allUnits~~]]}}~~
	[[systemChat~~]] [[~~str~~]] [[~~count~~]] [[~~allUnits]];		// Output the size of allUnits
			systemChat str count allUnits;
			</sqf>

	Now, what would the output of this look like?		Now, what would the output of this look like?
Line 111:		Line 115:

	A common mistake would be the following:		A common mistake would be the following:
	~~{{cc\|~~Create some [[Array~~\|array]]~~ containing three arrays.}}		<sqf>
	_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];		// Create some Array containing three arrays.
			_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];
	~~{{cc\|~~Wrongly use the [[select]] operator to get the count of the third array.}}
	[[count]] _arr [[select]] 2; ~~<span style="color: Red;">~~// Error</~~span~~>		// Wrongly use the select operator to get the count of the third array.
			count _arr select 2; // Error
			</sqf>

	Now, what went wrong?		Now, what went wrong?

	Let's put some brackets in the right places to make the mistake understandable:		Let's put some brackets in the right places to make the mistake understandable:
	([[count]] _arr) [[select]] 2; ~~<span style="color: Red;">~~// Error</~~span~~>		<sqf>(count _arr) select 2; // Error</sqf>

	Due to the nature of unary [[:Category:Scripting_Commands_Arma_3\|operators]], count instantly consumes our [[Variables\|variable]] ''_arr'' and returns the number ''3''.		Due to the nature of unary [[:Category:Scripting_Commands_Arma_3\|operators]], count instantly consumes our [[Variables\|variable]] ''_arr'' and returns the number ''3''.
Line 127:		Line 133:
	To do it correctly, one would have to put the {{ic\|_arr select 2}} in brackets.		To do it correctly, one would have to put the {{ic\|_arr select 2}} in brackets.
	The correct code thus would be:		The correct code thus would be:
	~~{{cc\|~~Create an [[Array~~\|array]]~~ containing three ~~[[Array\|arrays]]~~.}}		<sqf>
	_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];		// Create an Array containing three Arrays.
			_arr = [[1, 2, 3, 4, 5], [1, 2, 3, 4], [1, 2]];
	~~{{cc\|~~Use Brackets to correctly get count of the third [[Array~~\|array]].}}~~
	[[count]] (_arr [[select]] 2); ~~{{cc\|~~Good :) will evaluate to 2}}		// Use Brackets to correctly get count of the third Array
			count (_arr select 2); // Good :) will evaluate to 2
			</sqf>


	== Binary Operators ==		== Binary Operators ==

	Binary [[:Category:Scripting_Commands_Arma_3\|operators]] expect two arguments ({{ic\|<1st argument> binary <2nd argument>}}) and are executed according to their [[#precedence~~\|precedence]]~~. If their ~~[[#precedence\|~~precedence]] is equal, they are executed left to right.		Binary [[:Category:Scripting_Commands_Arma_3\|operators]] expect two arguments ({{ic\|<1st argument> binary <2nd argument>}}) and are executed according to their {{HashLink\|#precedence}}. If their precedence is equal, they are executed left to right.

	As example, we will look into the following expression:		As example, we will look into the following expression:
	~~{{cc\|~~Create a nested [[Array~~\|array]]~~ with 5 levels.}}		<sqf>
	_arr = [[[[[1]]]]];		// Create a nested Array with 5 levels.
			_arr = [[[[[1]]]]];
	~~{{cc\|~~Receive the nested number with some random math expressions.}}
	_arr [[select]] 0 [[select]] 1 [[-]] 1 [[select]] 15 ~~[[a_/_b\|~~/]] 3 [[-]] 5 [[select]] 0 [[select]] 10 ~~[[a__b\|~~]] 10 [[+]] 4 ~~[[a__b\|~~]] 0 [[-]] 100 ~~{{cc\|~~Evaluates to 1.}}		// Receive the nested number with some random math expressions.
			_arr select 0 select 1 - 1 select 15 / 3 - 5 select 0 select 10 * 10 + 4 * 0 - 100 // Evaluates to 1.
			</sqf>

	Now, let us analyze why this is happening for the first few expressions:		Now, let us analyze why this is happening for the first few expressions:
Line 156:		Line 166:

	If we now would put brackets at the correct spots, the expression will get clearer:		If we now would put brackets at the correct spots, the expression will get clearer:
	((((_arr [[select]] 0) [[select]] (1 [[-]] 1)) [[select]] ((15 ~~[[a_~~/~~_b\|/]]~~ 3) [[-]] 5)) [[select]] 0) [[select]] (((10 ~~[[a__b\|~~]] 10) [[+]] (4 ~~[[a__b\|~~]] 0)) [[-]] 100)		<sqf>((((_arr select 0) select (1 - 1)) select ((15 / 3) - 5)) select 0) select (((10 * 10) + (4 * 0)) - 100)</sqf>

	As you can see the [[a__b\|]] and [[a_/_b\|/]] are executed first which matches their [[Order of Precedence\|precedence]].		As you can see the [[a__b\|]] and [[a_/_b\|/]] are executed first which matches their [[Order of Precedence\|precedence]].

← Older revision		Revision as of 15:59, 2 November 2023
Line 13:		Line 13:
	In fact: there are barely any actual language structures at all.		In fact: there are barely any actual language structures at all.

	The functionality is provided via so called ''[[:Category:~~Scripting_Commands_Arma_3~~\|operators]]'' (or more commonly known [[:Category:~~Scripting_Commands_Arma_3~~\|scripting commands]]).		The functionality is provided via so called ''[[:Category:Arma 3: Scripting Commands\|operators]]'' (or more commonly known [[:Category:Arma 3: Scripting Commands\|scripting commands]]).
	Those [[:Category:Scripting Commands Arma 3\|operators]] are one of the following types: [[#Nular Operators\|Nular]]{{sic}}, [[#Unary Operators\|Unary]], or [[#Binary Operators\|Binary]].		Those [[:Category:Scripting Commands Arma 3\|operators]] are one of the following types: [[#Nular Operators\|Nular]]{{sic}}, [[#Unary Operators\|Unary]], or [[#Binary Operators\|Binary]].

Line 73:		Line 73:
	<sqf>1 + /* some random comment in an expression */ 1</sqf>		<sqf>1 + /* some random comment in an expression */ 1</sqf>

	It should be mentioned that there is a [[comment]] unary [[:Category:~~Scripting_Commands_Arma_3~~\|operator]] that should not be used as it will actually be executed (thus taking time to execute) but does nothing besides consuming a [[String\|string]].		It should be mentioned that there is a [[comment]] unary [[:Category:Arma 3: Scripting Commands\|operator]] that should not be used as it will actually be executed (thus taking time to execute) but does nothing besides consuming a [[String\|string]].
	There is no benefit in using it and the reason it exists is solely for backward compatibility.		There is no benefit in using it and the reason it exists is solely for backward compatibility.
	Another way to make a ''comment'' that way, is to just place a [[String\|string]]: <sqf inline>/* some code /; "i can be considered as a comment but should not be used"; / some other code */</sqf>		Another way to make a ''comment'' that way, is to just place a [[String\|string]]: <sqf inline>/* some code / "I can be considered as a comment but should not be used"; / some other code */</sqf>

	''Comments are removed during the [[PreProcessor_Commands\|preprocessing]] phase.'' This is important to know as that prevents usage in e.g a [[String\|string]] that gets compiled using the [[compile]] unary [[:Category:Scripting Commands\|operator]] or when only using [[loadFile]].		''Comments are removed during the [[PreProcessor_Commands\|preprocessing]] phase.'' This is important to know as that prevents usage in e.g a [[String\|string]] that gets compiled using the [[compile]] unary [[:Category:Scripting Commands\|operator]] or when only using [[loadFile]].
Line 82:		Line 82:
	== Nular Operators ==		== Nular Operators ==

	A {{sic\|nular}} operator is more or less a computed [[Variables\|variable]]. Each time accessed, it will return the current state of something.		A {{sic\|nular\|nullar}} operator is more or less a computed [[Variables\|variable]]. Each time accessed, it will return the current state of something.
	It is tempting to think of a nular{{sic}} [[:Category:~~Scripting_Commands_Arma_3~~\|operator]] as nothing more but a magic [[Variables\|global variable]], but it is important to differentiate!		It is tempting to think of a nular{{sic}} [[:Category:Arma 3: Scripting Commands\|operator]] as nothing more but a magic [[Variables\|global variable]], but it is important to differentiate!

	Consider following example in a mission with e.g. 5 units:		Consider following example in a mission with e.g. 5 units:
Line 115:		Line 115:
	== Unary Operators ==		== Unary Operators ==

	The unary [[:Category:~~Scripting_Commands_Arma_3~~\|operators]] are ~~[[:Category:Scripting_Commands_Arma_3\|~~operators]] that expect an argument on their right side ({{hl\|unary <argument>}}). They always will take the first argument that occurs.		The unary [[:Category:Arma 3: Scripting Commands\|operators]] are operators that expect an argument on their right side ({{hl\|unary <argument>}}). They always will take the first argument that occurs.

	A common mistake would be the following:		A common mistake would be the following:
Line 131:		Line 131:
	<sqf>(count _arr) select 2; // error</sqf>		<sqf>(count _arr) select 2; // error</sqf>

	Due to the nature of unary [[:Category:~~Scripting_Commands_Arma_3~~\|operators]], count instantly consumes our [[Variables\|variable]] ''_arr'' and returns the number ''3''.		Due to the nature of unary [[:Category:Arma 3: Scripting Commands\|operators]], count instantly consumes our [[Variables\|variable]] ''_arr'' and returns the number ''3''.
	The ''3'' then is passed to [[select]] which does not knows what to do with a number as left argument and thus errors out.		The ''3'' then is passed to [[select]] which does not knows what to do with a number as left argument and thus errors out.

Line 147:		Line 147:
	== Binary Operators ==		== Binary Operators ==

	Binary [[:Category:~~Scripting_Commands_Arma_3~~\|operators]] expect two arguments ({{hl\|<1st argument> binary <2nd argument>}}) and are executed according to their {{Link\|#precedence}}. If their precedence is equal, they are executed left to right.		Binary [[:Category:Arma 3: Scripting Commands\|operators]] expect two arguments ({{hl\|<1st argument> binary <2nd argument>}}) and are executed according to their {{Link\|#precedence}}. If their precedence is equal, they are executed left to right.

	As example, we will look into the following expression:		As example, we will look into the following expression:
Line 171:		Line 171:
	<sqf>((((_arr select 0) select (1 - 1)) select ((15 / 3) - 5)) select 0) select (((10 * 10) + (4 * 0)) - 100)</sqf>		<sqf>((((_arr select 0) select (1 - 1)) select ((15 / 3) - 5)) select 0) select (((10 * 10) + (4 * 0)) - 100)</sqf>

	As you can see the ~~[[a_~~~~_b\|]]~~ and ~~[[a_~~/~~_b\|~~/]] are executed first which matches their [[Order of Precedence\|precedence]].		As you can see the <sqf inline>*</sqf> and <sqf inline>/</sqf> are executed first which matches their [[Order of Precedence\|precedence]].
	Afterward, the [[+]] and [[-]] [[:Category:Scripting Commands\|operators]] will get executed followed by our [[select]] operator, which are executed from the left to the right.		Afterward, the <sqf inline>+</sqf> and <sqf inline>-</sqf> [[:Category:Scripting Commands\|operators]] will get executed followed by our [[select]] operator, which are executed from the left to the right.



	[[Category: Syntax]]		[[Category: Syntax]]

SQF Syntax - Revision history

Lou Montana: Fix example

Lou Montana: Fix semicolon

Lou Montana: Text replacement - "\{\{ *Wikipedia *\| *([-(){}a-zA-Z0-9_#':%\/\\]+) *\| *([-(){}a-zA-Z0-9_#':%\/\\ ]+) *\}\}" to "{{Link|https://en.wikipedia.org/wiki/$1|$2}}"

Lou Montana: Text replacement - "Link\|https:\/\/en\.wikipedia\.org\/([^w][^i])" to "Link|https://en.wikipedia.org/wiki/$1"

Lou Montana: Text replacement - "\{\{Wikipedia *\| *([a-zA-Z0-9_#]+) *\| *([a-zA-Z0-9_ #]+) *\}\}" to "{{Link|https://en.wikipedia.org/$1|$2}}"

Lou Montana: Text replacement - "{{HashLink" to "{{Link"

Lou Montana: Some wiki formatting

Lou Montana: Some wiki formatting

Lou Montana: Some wiki formatting

Lou Montana: Some wiki formatting

Lou Montana: Text replacement - "\{\{ Wikipedia \| ([-(){}a-zA-Z0-9_#':%\/\\]+) \| ([-(){}a-zA-Z0-9_#':%\/\\ ]+) \}\}" to "{{Link|https://en.wikipedia.org/wiki/$1|$2}}"

Lou Montana: Text replacement - "\{\{Wikipedia \| ([a-zA-Z0-9_#]+) \| ([a-zA-Z0-9_ #]+) *\}\}" to "{{Link|https://en.wikipedia.org/$1|$2}}"