parsingNamespace: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Command Group: Variables)
m (Text replacement - "‎" to "")
 
(60 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Command|= Comments
{{RV|type=command
____________________________________________________________________________________________


| arma2 |= Game name
|game1= arma2
|version1= 1.00


|1.00|= Game version
|game2= arma2oa
____________________________________________________________________________________________
|version2= 1.50


| Returns the global namespace attached to config parser. |= Description
|game3= tkoh
____________________________________________________________________________________________
|version3= 1.00


| '''parsingNamespace''' |= Syntax
|game4= arma3
|version4= 0.50


|p1= |= PARAMETER1
|gr1= Namespaces
|gr2= Variables


|p2= |= PARAMETER2
|descr= Returns the global namespace attached to config parser.


|p3= |= PARAMETER3
|s1= [[parsingNamespace]]


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


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


|x1= <code>'''parsingNamespace''' [[setVariable]] ["var1",101.23124];
|seealso= [[missionNamespace]] [[uiNamespace]] [[currentNamespace]] [[profileNamespace]] [[localNamespace]] [[allVariables]] [[with]] [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]]
_profVar1 = '''parsingNamespace''' [[getVariable]] "var1";</code>|= EXAMPLE1
 
____________________________________________________________________________________________
 
| [[missionNamespace]], [[uiNamespace]], [[currentNamespace]], [[profileNamespace]], [[with]], [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]] |= SEEALSO
 
|  |= MPBEHAVIOUR
____________________________________________________________________________________________
}}
}}


<h3 style='display:none'>Notes</h3>
{{Note
<dl class='command_description'>
|user= BrotherhoodOfHam
<!-- Note Section BEGIN -->
|timestamp= 20150127180800
 
|text= Any global variable defined in a config using __EXEC() will be stored in this namespace.<br>
<!-- Note Section END -->
For example in the description.ext:<br>
</dl>
<sqf>__EXEC(testVar = 1);</sqf>
 
<h3 style='display:none'>Bottom Section</h3>
[[Category:ArmA 2: New Scripting Commands List|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
[[Category:Command_Group:_Variables|{{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]]
The variable "testVar" can be accessed during mission run time using [[getVariable]]
<code>[[hint]] [[str]] ([[parsingNamespace]] [[getVariable]] ["testVar", 0]);</code>
<sqf>hint str (parsingNamespace getVariable ["testVar", 0]);</sqf>
The above example would print 1.<br/><br/>
The above example would print 1.<br><br>
This example however:
This example however:
<code>__EXEC(_testVar = 1);</code>
<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()
</dd>
}}
</dl>
<!-- DISCONTINUE Notes -->

Latest revision as of 12:55, 26 April 2023

Logo A2.png1.00A2 OA Logo.png1.50tkoh logo small.png1.00Arma 3 logo black.png0.50
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:
missionNamespace uiNamespace currentNamespace profileNamespace localNamespace allVariables with Forward 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()
Retrieved from "https://community.bistudio.com/wiki?title=parsingNamespace&oldid=339160"