parsingNamespace

From Bohemia Interactive Community
Revision as of 12:55, 26 April 2023 by Lou Montana (talk | contribs) (Text replacement - "‎" to "")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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:
Copy
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:
Copy
__EXEC(testVar = 1);
The variable "testVar" can be accessed during mission run time using getVariable
Copy
hint str (parsingNamespace getVariable ["testVar", 0]);
The above example would print 1.

This example however:
Copy
__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"