parsingNamespace: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "<br/>" to "<br>")
m (Text replacement - "[[Category:Scripting_Commands_Take_On_Helicopters" to "[[Category:Scripting Commands Take On Helicopters")
Line 43: Line 43:
[[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[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}}}}]]
[[Category:Command_Group:_Variables|{{uc:{{PAGENAME}}}}]]
[[Category:Command_Group:_Variables|{{uc:{{PAGENAME}}}}]]

Revision as of 15:11, 6 April 2020

Hover & click on the images for description

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

See also:
missionNamespaceuiNamespacecurrentNamespaceprofileNamespacewithForward 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

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 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()