parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$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 41: | Line 41: | ||
The above example would print 1.<br><br> | The above example would print 1.<br><br> | ||
This example however: | This example however: | ||
< | <sqf>__EXEC(_testVar = 1);</sqf> | ||
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> | 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() | See [[PreProcessor Commands]] for more details on __EXEC() |
Revision as of 10:58, 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 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()