parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Waffle SS. (talk | contribs) No edit summary |
No edit summary |
||
| Line 45: | Line 45: | ||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] | ||
<!-- CONTINUE Notes --> | |||
<dl class="command_description"> | |||
<dd class="notedate">Posted on January 27, 2015 - 18:08 (UTC)</dd> | |||
<dt class="note">[[User:BrotherhoodOfHam|BrotherhoodOfHam]]</dt> | |||
<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/> | |||
<code>__EXEC(testVar = 1);</code> | |||
The variable "testVar" can be accessed during mission run time using [[getVariable]] | |||
<code>[[hint]] [[str]] ([[parsingNamespace]] [[getVariable]] ["testVar", 0]);</code> | |||
The above example would print 1.<br/><br/> | |||
This example however: | |||
<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. | |||
</dd> | |||
</dl> | |||
<!-- DISCONTINUE Notes --> | |||
Revision as of 19:08, 27 January 2015
Description
- Description:
- Return 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.