parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 58: | Line 58: | ||
This example however: | This example however: | ||
<code>__EXEC(_testVar = 1);</code> | <code>__EXEC(_testVar = 1);</code> | ||
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. | 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.<br/><br/> | ||
See [[PreProcessor Commands]] for more details on __EXEC() | |||
</dd> | </dd> | ||
</dl> | </dl> | ||
<!-- DISCONTINUE Notes --> | <!-- DISCONTINUE Notes --> | ||
Revision as of 20:50, 27 January 2015
Description
- Description:
- Return the global namespace attached to config parser.
- Groups:
- Uncategorised
Syntax
- Syntax:
- parsingNamespace
- Return Value:
- Namespace
Examples
- Example 1:
parsingNamespace setVariable ["var1",101.23124]; _profVar1 = parsingNamespace getVariable "var1";
Additional Information
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
Notes
Bottom Section
- 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()