---
name: "parsingNamespace"
type: command
status: ok
groups: ["Namespaces", "Variables"]
arma3_since: "0.50"
locality: {"argument": null, "effect": null, "server_exec": false}
source: https://community.bistudio.com/wiki/parsingNamespace
revid: 339160
updated: 2023-04-26T10:55:24Z
---

# parsingNamespace

*Command · Namespaces, Variables · Arma 3 v0.50 · introduced in Arma 2 v1.00*

## Description

Returns the global namespace attached to config parser.

## Syntax

```sqf
parsingNamespace
```

**Returns:** [Namespace](../topics/Namespace.md)

## Examples

### Example 1

```sqf
parsingNamespace setVariable ["var1", 101.23124];
_profVar1 = parsingNamespace getVariable "var1";
```

## See also

[missionNamespace](../commands/missionNamespace.md) · [uiNamespace](../commands/uiNamespace.md) · [currentNamespace](../commands/currentNamespace.md) · [profileNamespace](../commands/profileNamespace.md) · [localNamespace](../commands/localNamespace.md) · [allVariables](../commands/allVariables.md) · [with](../commands/with.md) · ArmA: Editing

## Community notes

**BrotherhoodOfHam** — 2015-01-27

Any global variable defined in a config using __EXEC() will be stored in this namespace.

For example in the description.ext:

```sqf
__EXEC(testVar = 1);
```

The variable "testVar" can be accessed during mission run time using [getVariable](../commands/getVariable.md)

```sqf
hint str (parsingNamespace getVariable ["testVar", 0]);
```

The above example would print 1.

This example however:

```sqf
__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](../topics/PreProcessor_Commands.md) for more details on __EXEC()

<sub>Source: [BI Community Wiki — parsingNamespace](https://community.bistudio.com/wiki/parsingNamespace) (revision 339160).</sub>