Config Parser - Revision history

Lou Montana: Fix redirection

2021-08-16T12:03:57Z

Fix redirection

← Older revision		Revision as of 14:03, 16 August 2021
Line 1:		Line 1:
	#REDIRECT [[PreProcessor Commands]]		#REDIRECT [[PreProcessor Commands#Config Parser]]

Str: Redirected page to PreProcessor Commands

2011-10-23T09:39:31Z

Redirected page to PreProcessor Commands

← Older revision		Revision as of 11:39, 23 October 2011
Line 1:		Line 1:
	~~=Introduction =~~		#REDIRECT [[PreProcessor Commands]]
	~~(needed)~~


	~~= Parser commands/macros =~~

	~~==__EXEC==~~
	~~Allows you to assign values to variables. These variables can then be used to in other calculations, or output via the __EVAL macro.~~

	~~<code>__EXEC (_x = .345);~~
	~~__EXEC (_y = _y + 1);~~
	~~__EXEC (_str = format["name: %1",_name])</code>~~


	~~__EXEC terminates at the first closed parenthesis "''')'''" it encounters, so expressions like the following will cause an error:~~

	~~<code>__EXEC (_val = (_arr select 0)*10); // ILLEGAL!~~
	~~__EXEC (_str = (_this select 0) setDamage 1); // ILLEGAL!</code>~~

	~~==__EVAL==~~
	~~With this macro expressions can be evaluated, including previously assigned internal variables.~~

	~~<code>y = __EVAL (_y);~~
	~~text = __EVAL (_str1 + _str2);</code>~~


	~~Unlike the __EXEC command, __EVAL ''can'' contain other parentheses, making more complex, and even conditional operations possible:~~
	~~<code>x = __EVAL (if (_idx>5) then {0} else {.5});</code>~~


	~~If you need to make use of a~~ #~~defined value in your __EXEC or __EVAL string and you need to convert it to string using 'str', remember not to add extra brackets like this:~~
	~~<code>onSliderPosChanged = __EVAL("[" + str (MY_NUMERIC_DEFINE) + "] call compile preProcessFile 'my.sqf'");</code>~~
	~~The above will fail when parsing the __EVAL, the correct line would be:~~
	~~<code>onSliderPosChanged = __EVAL("[" + str MY_NUMERIC_DEFINE + "] call compile preProcessFile 'my.sqf'");</code>~~


	Be aware though, that if these evaluations are used in a mission's description.ext, that at that point the mission information is not available yet (i.e. the mission objects have not been created yet). (''At least in VBS2 this is the case.'')

	~~===Combine multiple stringtable keys===~~

	~~__EVAL("Default: " + localize "STR_AAS_EXT_DISABLED")~~
	~~__EVAL(localize "STR_AAS_EXT_DEFAULT" + localize "STR_AAS_EXT_DISABLED")~~

	~~This works in the [[Description.ext]] at least.~~

	~~[[category:Operation Flashpoint: Editing]]~~
	[[~~Category:ArmA: Addon Configuration~~]]

.kju: Added info how to "combine multiple stringtable keys"

2011-07-19T15:53:31Z

Added info how to "combine multiple stringtable keys"

← Older revision		Revision as of 17:53, 19 July 2011
Line 36:		Line 36:

	Be aware though, that if these evaluations are used in a mission's description.ext, that at that point the mission information is not available yet (i.e. the mission objects have not been created yet). (''At least in VBS2 this is the case.'')		Be aware though, that if these evaluations are used in a mission's description.ext, that at that point the mission information is not available yet (i.e. the mission objects have not been created yet). (''At least in VBS2 this is the case.'')

			===Combine multiple stringtable keys===

			__EVAL("Default: " + localize "STR_AAS_EXT_DISABLED")
			__EVAL(localize "STR_AAS_EXT_DEFAULT" + localize "STR_AAS_EXT_DISABLED")

			This works in the [[Description.ext]] at least.

	[[category:Operation Flashpoint: Editing]]		[[category:Operation Flashpoint: Editing]]
	[[Category:ArmA: Addon Configuration]]		[[Category:ArmA: Addon Configuration]]

Bn880 at 13:47, 9 September 2009

2009-09-09T13:47:36Z

← Older revision		Revision as of 15:47, 9 September 2009
Line 27:		Line 27:
	Unlike the __EXEC command, __EVAL ''can'' contain other parentheses, making more complex, and even conditional operations possible:		Unlike the __EXEC command, __EVAL ''can'' contain other parentheses, making more complex, and even conditional operations possible:
	<code>x = __EVAL (if (_idx>5) then {0} else {.5});</code>		<code>x = __EVAL (if (_idx>5) then {0} else {.5});</code>


			If you need to make use of a #defined value in your __EXEC or __EVAL string and you need to convert it to string using 'str', remember not to add extra brackets like this:
			<code>onSliderPosChanged = __EVAL("[" + str (MY_NUMERIC_DEFINE) + "] call compile preProcessFile 'my.sqf'");</code>
			The above will fail when parsing the __EVAL, the correct line would be:
			<code>onSliderPosChanged = __EVAL("[" + str MY_NUMERIC_DEFINE + "] call compile preProcessFile 'my.sqf'");</code>

Kronzky: /* __EXEC - added another example */

2009-07-17T22:07:38Z

__EXEC - added another example

← Older revision		Revision as of 00:07, 18 July 2009
Line 15:		Line 15:
	__EXEC terminates at the first closed parenthesis "''')'''" it encounters, so expressions like the following will cause an error:		__EXEC terminates at the first closed parenthesis "''')'''" it encounters, so expressions like the following will cause an error:

	<code>__EXEC (_val = (_arr select 0)*10); // ILLEGAL!</code>		<code>__EXEC (_val = (_arr select 0)*10); // ILLEGAL!
			__EXEC (_str = (_this select 0) setDamage 1); // ILLEGAL!</code>

	==__EVAL==		==__EVAL==

Kronzky: used more realistic examples

2008-11-05T17:11:16Z

used more realistic examples

← Older revision		Revision as of 19:11, 5 November 2008
Line 8:		Line 8:
	Allows you to assign values to variables. These variables can then be used to in other calculations, or output via the __EVAL macro.		Allows you to assign values to variables. These variables can then be used to in other calculations, or output via the __EVAL macro.

	<code>__EXEC (_y = _y + 1);		<code>__EXEC (_x = .345);
	__EXEC (_str = format["~~daytime~~: %1",~~dayTime~~])</code>		__EXEC (_y = _y + 1);
			__EXEC (_str = format["name: %1",_name])</code>


	__EXEC terminates at the first closed parenthesis "''')'''" it encounters, so expressions like the following will cause an error:		__EXEC terminates at the first closed parenthesis "''')'''" it encounters, so expressions like the following will cause an error:

	<code>__EXEC (_val = (~~_this~~ select 0)*10); // ILLEGAL!</code>		<code>__EXEC (_val = (_arr select 0)*10); // ILLEGAL!</code>

	==__EVAL==		==__EVAL==

Kronzky: it's a start...

2008-10-31T21:20:33Z

it's a start...

New page

=Introduction =
(needed)

= Parser commands/macros =

==__EXEC==
Allows you to assign values to variables. These variables can then be used to in other calculations, or output via the __EVAL macro.

<code>__EXEC (_y = _y + 1);
__EXEC (_str = format["daytime: %1",dayTime])</code>

__EXEC terminates at the first closed parenthesis "''')'''" it encounters, so expressions like the following will cause an error:

<code>__EXEC (_val = (_this select 0)*10); // ILLEGAL!</code>

==__EVAL==
With this macro expressions can be evaluated, including previously assigned internal variables.

<code>y = __EVAL (_y);
text = __EVAL (_str1 + _str2);</code>

Unlike the __EXEC command, __EVAL ''can'' contain other parentheses, making more complex, and even conditional operations possible:
<code>x = __EVAL (if (_idx>5) then {0} else {.5});</code>

Be aware though, that if these evaluations are used in a mission's description.ext, that at that point the mission information is not available yet (i.e. the mission objects have not been created yet). (''At least in VBS2 this is the case.'')

[[category:Operation Flashpoint: Editing]]
[[Category:ArmA: Addon Configuration]]