{"name":"parsingNamespace","title":"parsingNamespace","type":"command","url":"https://community.bistudio.com/wiki/parsingNamespace","revid":339160,"updated":"2023-04-26T10:55:24Z","groups":["Namespaces","Variables"],"status":"ok","games":{"arma2":"1.00","arma2oa":"1.50","tkoh":"1.00","arma3":"0.50"},"since":"arma2 1.00","arma3_since":"0.50","description":"Returns the global namespace attached to config parser.","syntaxes":[{"syntax":"parsingNamespace","params":[],"returns":{"type":"Namespace","type_expr":"Namespace"},"form":"nullary"}],"examples":[{"code":["parsingNamespace setVariable [\"var1\", 101.23124];\n_profVar1 = parsingNamespace getVariable \"var1\";"]}],"see_also":["missionNamespace","uiNamespace","currentNamespace","profileNamespace","localNamespace","allVariables","with","ArmA: Editing"],"notes":[{"user":"BrotherhoodOfHam","date":"2015-01-27T18:08:00Z","text":"Any global variable defined in a config using __EXEC() will be stored in this namespace.\nFor example in the description.ext:\n\n```sqf\n__EXEC(testVar = 1);\n```\n\nThe variable \"testVar\" can be accessed during mission run time using getVariable\n\n```sqf\nhint str (parsingNamespace getVariable [\"testVar\", 0]);\n```\n\nThe above example would print 1.\n\nThis example however:\n\n```sqf\n__EXEC(_testVar = 1);\n```\n\nWould 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.\n\nSee PreProcessor Commands for more details on __EXEC()"}]}