parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\|seealso= ([^ ]+)\]\], *\[\[" to "|seealso= $1]] [[") |
Lou Montana (talk | contribs) m (Some wiki formatting) |
||
Line 33: | Line 33: | ||
|user= BrotherhoodOfHam | |user= BrotherhoodOfHam | ||
|timestamp= 20150127180800 | |timestamp= 20150127180800 | ||
|text= | |text= 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> | <sqf>__EXEC(testVar = 1);</sqf> |
Revision as of 00:31, 31 August 2022
Description
- Description:
- Returns the global namespace attached to config parser.
- Groups:
- NamespacesVariables
Syntax
- Syntax:
- parsingNamespace
- Return Value:
- Namespace
Examples
- Example 1:
Additional Information
- See also:
- missionNamespace uiNamespace currentNamespace profileNamespace localNamespace allVariables with Forward 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 Jan 27, 2015 - 18:08 (UTC)
-
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 getVariableThe above example would print 1.
This example however: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()