parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "{{uc:{{PAGENAME}}}} " to "") |
Lou Montana (talk | contribs) m (Text replacement - " \| arma2 \| *([0-9]\.[0-9]{2}) * " to " | arma2 |$1 |game2= arma2oa |version2= 1.50 |game3= tkoh |version3= 1.00 |game4= arma3 |version4= 0.50 ") |
||
| Line 2: | Line 2: | ||
| arma2 | | arma2 | ||
|1.00 | |||
|game2= arma2oa | |||
|version2= 1.50 | |||
|game3= tkoh | |||
|version3= 1.00 | |||
| | |game4= arma3 | ||
|version4= 0.50 | |||
|gr1= Variables | |gr1= Variables | ||
Revision as of 20:30, 9 June 2021
Description
- Description:
- Description needed
- Groups:
- Variables
Syntax
- Syntax:
- Syntax needed
- Return Value:
- Return value needed
Examples
- Example 1:
parsingNamespace setVariable ["var1",101.23124]; _profVar1 = parsingNamespace getVariable "var1";
Additional Information
- See also:
- See also needed
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on January 27, 2015 - 18:08 (UTC)
- BrotherhoodOfHam
Any global variable defined in a config using __EXEC() will be stored in this namespace.
For example in the description.ext:
__EXEC(testVar = 1);The variable "testVar" can be accessed during mission run time using getVariablehint str (parsingNamespace getVariable ["testVar", 0]);The above example would print 1.
This example however:__EXEC(_testVar = 1);Would print 0, because adding an underscore will make the variable local to the config in the same way that it would make it local to a script.
See PreProcessor Commands for more details on __EXEC()