parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\| (\[\[[a-zA-Z0-9 _]+\]\][^ ]*) \}\}" to "|seealso= $1 }}") |
Lou Montana (talk | contribs) m (Text replacement - " \| *('''[a-zA-Z0-9]+''') \|r1=" to " \|s1= $1 |r1=") |
||
| Line 17: | Line 17: | ||
| Returns the global namespace attached to config parser. | | Returns the global namespace attached to config parser. | ||
| '''parsingNamespace''' | \|s1= '''parsingNamespace''' | ||
|r1= [[Namespace]] | |r1= [[Namespace]] | ||
Revision as of 15:41, 13 June 2021
Description
- Description:
- Description needed
- Groups:
- Variables
Syntax
- Syntax:
- parsingNamespace
- Return Value:
- Namespace
Examples
- Example 1:
parsingNamespace setVariable ["var1",101.23124]; _profVar1 = parsingNamespace getVariable "var1";
Additional Information
- See also:
- missionNamespaceuiNamespacecurrentNamespaceprofileNamespacelocalNamespaceallVariableswithForward Compatibility
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()