parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\|x([0-9])= *<code>([^<]*)<\/code>" to "|x$1= <sqf>$2</sqf>") |
Lou Montana (talk | contribs) m (Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>") |
||
| Line 36: | Line 36: | ||
<dd class="note"><br>Any global variable defined in a config using __EXEC() will be stored in this namespace.<br> | <dd class="note"><br>Any global variable defined in a config using __EXEC() will be stored in this namespace.<br> | ||
For example in the description.ext:<br> | For example in the description.ext:<br> | ||
< | <sqf>__EXEC(testVar = 1);</sqf> | ||
The variable "testVar" can be accessed during mission run time using [[getVariable]] | The variable "testVar" can be accessed during mission run time using [[getVariable]] | ||
<code>hint str (parsingNamespace getVariable ["testVar", 0]);</code> | <code>hint str (parsingNamespace getVariable ["testVar", 0]);</code> | ||
Revision as of 10:57, 13 May 2022
Description
- Description:
- Returns the global namespace attached to config parser.
- Groups:
- NamespacesVariables
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:
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()