parsingNamespace: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "(\|p[0-9]+ *= * )+" to "")
m (Text replacement - "<dl class="command_description"> <dd class="notedate">" to "<dl class="command_description"> <dt></dt> <dd class="notedate">")
Line 27: Line 27:
<!-- CONTINUE Notes -->
<!-- CONTINUE Notes -->
<dl class="command_description">
<dl class="command_description">
<dt></dt>
<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>

Revision as of 13:36, 5 April 2021

Hover & click on the images for description

Description

Description:
Description needed
Groups:
Variables

Syntax

Syntax:
Syntax needed
Return Value:
Return value needed

Examples

Example 1:
parsingNamespace setVariable ["var1",101.23124]; _profVar1 = parsingNamespace getVariable "var1";

Additional Information

See also:
See also needed

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:
__EXEC(testVar = 1); The variable "testVar" can be accessed during mission run time using getVariable hint 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()