parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "Category:Scripting Commands ArmA2" to "Category:Scripting Commands Arma 2") |
Lou Montana (talk | contribs) m (Text replacement - "<br/>" to "<br>") |
||
| Line 51: | Line 51: | ||
<dd class="notedate">Posted on January 27, 2015 - 18:08 (UTC)</dd> | <dd class="notedate">Posted on January 27, 2015 - 18:08 (UTC)</dd> | ||
<dt class="note">[[User:BrotherhoodOfHam|BrotherhoodOfHam]]</dt> | <dt class="note">[[User:BrotherhoodOfHam|BrotherhoodOfHam]]</dt> | ||
<dd class="note"><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> | ||
<code>__EXEC(testVar = 1);</code> | <code>__EXEC(testVar = 1);</code> | ||
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> | ||
The above example would print 1.<br | The above example would print 1.<br><br> | ||
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.<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() | ||
</dd> | </dd> | ||
</dl> | </dl> | ||
<!-- DISCONTINUE Notes --> | <!-- DISCONTINUE Notes --> | ||
Revision as of 14:37, 14 March 2020
Description
- Description:
- Returns 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()