parsingNamespace: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>")
m (Some wiki formatting)
Line 18: Line 18:
|descr= Returns the global namespace attached to config parser.
|descr= Returns the global namespace attached to config parser.


|s1= '''parsingNamespace'''
|s1= [[parsingNamespace]]


|r1= [[Namespace]]
|r1= [[Namespace]]


|x1= <sqf>'''parsingNamespace''' setVariable ["var1",101.23124];
|x1= <sqf>
_profVar1 = '''parsingNamespace''' getVariable "var1";</sqf>
parsingNamespace setVariable ["var1", 101.23124];
_profVar1 = parsingNamespace getVariable "var1";
</sqf>


|seealso= ‎[[missionNamespace]], [[uiNamespace]], [[currentNamespace]], [[profileNamespace]], [[localNamespace]], [[allVariables]], [[with]], [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]]
|seealso= ‎[[missionNamespace]], [[uiNamespace]], [[currentNamespace]], [[profileNamespace]], [[localNamespace]], [[allVariables]], [[with]], [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]]
}}
}}


 
{{Note
<dl class="command_description">
|user= BrotherhoodOfHam
 
|timestamp= 20150127180800
<dt></dt>
|text= <br>Any global variable defined in a config using __EXEC() will be stored in this namespace.<br>
<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>
For example in the description.ext:<br>
<sqf>__EXEC(testVar = 1);</sqf>
<sqf>__EXEC(testVar = 1);</sqf>
Line 44: Line 43:
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()
</dd>
}}
 
</dl>

Revision as of 13:52, 22 May 2022

Hover & click on the images for description

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
BrotherhoodOfHam - c
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:
__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()