Namespace

In computing, a namespace is a set of signs ("names") that are used to identify and refer to objects of various kinds. A namespace ensures that all of a given set of objects have unique names so that they can be easily identified.
Namespaces are commonly structured as hierarchies to allow reuse of names in different contexts. As an analogy, consider a system of naming of people where each person has a given name, as well as a family name shared with their relatives. If the first names of family members are unique only within each family, then each person can be uniquely identified by the combination of first name and family name; there is only one Jane Doe, though there may be many Janes. Within the namespace of the Doe family, just "Jane" suffices to unambiguously designate this person, while within the "global" namespace of all people, the full name must be used.
Prominent examples for namespaces include file systems, which assign names to files.
Some programming languages organize their variables and subroutines in namespaces.
Computer networks and distributed systems assign names to resources, such as computers, printers, websites, and remote files. Operating systems can partition kernel resources by isolated namespaces to support virtualization containers.
In a similar manner, hierarchical file systems organize files in directories. Each directory is a separate namespace, so that the directories "letters" and "invoices" may both contain a file "to_jane".
In computer programming, namespaces are typically employed for the purpose of grouping symbols and identifiers around a particular functionality and to avoid name collisions between multiple identifiers that share the same name.
In networking, the Domain Name System organizes websites (and other resources) into hierarchical namespaces.
Name conflicts.
Element names are defined by the developer. This often results in a conflict when trying to mix XML documents from different XML applications.
This XML carries HTML table information:
<table>
 <tr>
 <td>Apples</td>
 <td>Oranges</td>
 </tr>
</table>
This XML carries information about a table (i.e. a piece of furniture):
<table>
 <name>African Coffee Table</name>
 <width>80</width>
 <length>120</length>
</table>
If these XML fragments were added together, there would be a name conflict. Both contain a element, but the elements have different content and meaning.
An XML parser will not know how to handle these differences.
Solution via prefix.
Name conflicts in XML can easily be avoided using a name prefix.
The following XML distinguishes between information about the HTML table and furniture by prefixing "h" and "f" at the beginning of the elements.
<h:table>
 <h:tr>
 <h:td>Apples</h:td>
 <h:td>Oranges</h:td>
 </h:tr>
</h:table>
<f:table>
 <f:name>African Coffee Table</f:name>
 <f:width>80</f:width>
 <f:length>120</f:length>
</f:table>
Naming system.
A name in a namespace consists of a namespace identifier and a local name. The namespace name is usually applied as a prefix to the local name.
In augmented Backus–Naur form:
 name = <namespace identifier> separator <local name>
When local names are used by themselves, name resolution is used to decide which (if any) particular name is alluded to by some particular local name.
Delegation.
Delegation of responsibilities between parties is important in real-world applications, such as the structure of the World Wide Web. Namespaces allow delegation of identifier assignment to multiple name issuing organisations whilst retaining global uniqueness. A central Registration authority registers the assigned namespace identifiers allocated. Each namespace identifier is allocated to an organisation which is subsequently responsible for the assignment of names in their allocated namespace. This organisation may be a name issuing organisation that assign the names themselves, or another Registration authority which further delegates parts of their namespace to different organisations.
Hierarchy.
A naming scheme that allows subdelegation of namespaces to third parties is a hierarchical namespace.
A hierarchy is recursive if the syntax for the namespace identifiers is the same for each subdelegation. An example of a recursive hierarchy is the Domain name system.
An example of a non-recursive hierarchy are Uniform Resource Name representing an Internet Assigned Numbers Authority (IANA) number.
Namespace versus scope.
A namespace identifier may provide context (scope in computer science) to a name, and the terms are sometimes used interchangeably. However, the context of a name may also be provided by other factors, such as the location where it occurs or the syntax of the name.
In programming languages.
For many programming languages, namespace is a context for their identifiers. In an operating system, an example of namespace is a directory. Each name in a directory uniquely identifies one file or subdirectory.
As a rule, names in a namespace cannot have more than one meaning; that is, different meanings cannot share the same name in the same namespace. A namespace is also called a context, because the same name in different namespaces can have different meanings, each one appropriate for its namespace.
Following are other characteristics of namespaces:
As well as its abstract language technical usage as described above, some languages have a specific keyword used for explicit namespace control, amongst other uses. Below is an example of a namespace in C++:
// This is how one brings a name into the current scope. In this case, it's
// bringing them into global scope.
using std::cout;
using std::endl;
namespace box1 {
 int box_side = 4;
namespace box2 {
 int box_side = 12;
int main() {
 int box_side = 42;
 cout « box1::box_side « endl; // Outputs 4.
 cout « box2::box_side « endl; // Outputs 12.
 cout « box_side « endl; // Outputs 42.
Computer-science considerations.
A namespace in computer science (sometimes also called a name scope), is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols (i.e. names). An identifier defined in a namespace is associated only with that namespace. The same identifier can be independently defined in multiple namespaces. That is, an identifier defined in one namespace may or may not have the same meaning as the same identifier defined in another namespace. Languages that support namespaces specify the rules that determine to which namespace an identifier (not its definition) belongs.
This concept can be illustrated with an analogy. Imagine that two companies, X and Y, each assign ID numbers to their employees. X should not have two employees with the same ID number, and likewise for Y; but it is not a problem for the same ID number to be used at both companies. For example, if Bill works for company X and Jane works for company Y, then it is not a problem for each of them to be employee #123. In this analogy, the ID number is the identifier, and the company serves as the namespace. It does not cause problems for the same identifier to identify a different person in each namespace.
In large computer programs or documents it is common to have hundreds or thousands of identifiers. Namespaces (or a similar technique, see Emulating namespaces) provide a mechanism for hiding local identifiers. They provide a means of grouping logically related identifiers into corresponding namespaces, thereby making the system more modular.
Data storage devices and many modern programming languages support namespaces. Storage devices use directories (or folders) as namespaces. This allows two files with the same name to be stored on the device so long as they are stored in different directories. In some programming languages (e.g. C++, Python), the identifiers naming namespaces are themselves associated with an enclosing namespace. Thus, in these languages namespaces can nest, forming a namespace tree. At the root of this tree is the unnamed global namespace.
Use in common languages.
It is possible to use anonymous structs as namespaces in C since C99.
// helper.c
static int _add(int a, int b) {
 return a + b;
const struct {
 double pi;
 int (*add) (int, int);
} helper = { 3.14, _add };
// helper.h
const struct {
 double pi;
 int (*add) (int, int);
} helper;
// main.c
int main(){
 printf("3 + 2 = %d\n", helper.add(3, 2));
 printf("pi is %f\n", helper.pi);
In C++, a namespace is defined with a namespace block.
namespace abc {
 int bar;
Within this block, identifiers can be used exactly as they are declared. Outside of this block, the namespace specifier must be prefixed. For example, outside of codice_1, codice_2 must be written codice_3 to be accessed. C++ includes another construct that makes this verbosity unnecessary. By adding the line
using namespace abc;
to a piece of code, the prefix codice_4 is no longer needed.
Identifiers that are not explicitly declared within a namespace are considered to be in the global namespace.
int foo;
These identifiers can be used exactly as they are declared, or, since the global namespace is unnamed, the namespace specifier codice_5 can be prefixed. For example, codice_6 can also be written codice_7.
Namespace resolution in C++ is hierarchical. This means that within the hypothetical namespace codice_8, the identifier codice_9 refers to codice_10. If codice_10 doesn't exist, it then refers to codice_12. If neither codice_10 nor codice_12 exist, codice_9 refers to codice_16, an identifier in the global namespace.
Namespaces in C++ are most often used to avoid naming collisions. Although namespaces are used extensively in recent C++ code, most older code does not use this facility because it did not exist in early versions of the language. For example, the entire C++ Standard Library is defined within codice_17, but before standardization many components were originally in the global namespace. A programmer can insert the codice_18 directive to bypass namespace resolution requirements and obtain backwards compatibility with older code that expects all identifiers to be in the global namespace. However the use of the codice_18 directive for reasons other than backwards compatibility (e.g., convenience) is considered to be against good code practices.
In Java, the idea of a namespace is embodied in Java packages. All code belongs to a package, although that package need not be explicitly named. Code from other packages is accessed by prefixing the package name before the appropriate identifier, for example codice_20 in codice_21 can be referred to as codice_22 (this is known as the fully qualified class name). Like C++, Java offers a construct that makes it unnecessary to type the package name (codice_23). However, certain features (such as reflection) require the programmer to use the fully qualified name.
Unlike C++, namespaces in Java are not hierarchical as far as the syntax of the language is concerned. However, packages are named in a hierarchical manner. For example, all packages beginning with codice_24 are a part of the Java platform—the package contains classes core to the language, and contains core classes specifically relating to reflection.
In Java (and Ada, C#, and others), namespaces/packages express semantic categories of code. For example, in C#, codice_25 contains code provided by the system (the .NET Framework). How specific these categories are and how deep the hierarchies go differ from language to language.
Function and class scopes can be viewed as implicit namespaces that are inextricably linked with visibility, accessibility, and object lifetime.
Namespaces are heavily used in C# language. All .NET Framework classes are organized in namespaces, to be used more clearly and to avoid chaos. Furthermore, custom namespaces are extensively used by programmers, both to organize their work and to avoid naming collisions.
When referencing a class, one should specify either its fully qualified name, which means namespace followed by the class name,
System.Console.WriteLine("Hello World!");
int i = System.Convert.ToInt32("123");
or add a using statement. This, eliminates the need to mention the complete name of all classes in that namespace.
using System;
Console.WriteLine("Hello World!");
int i = Convert.ToInt32("123");
In the above examples, System is a namespace, and Console and Convert are classes defined within System.
In Python, namespaces are defined by the individual modules, and since modules can be contained in hierarchical packages, then namespaces are hierarchical too.
In general when a module is imported then the names defined in the module are defined via that module's namespace, and are accessed in from the calling modules by using the fully qualified name.
import Modulea
Modulea.func1()
Modulea.func2()
a = Modulea.Class1()
The codice_26 statement can be used to insert the relevant names directly into the calling module's namespace, and those names can be accessed from the calling module without the qualified name:
from Modulea import func1
func1()
func2() # this will fail as an undefined name, as will the full name Modulea.func2()
a = Class1() # this will fail as an undefined name, as will the full name Modulea.Class1()
Since this directly imports names (without qualification) it can overwrite existing names with no warnings.
A special form of the statement is codice_27 which imports all names defined in the named package directly in the calling module's namespace. Use of this form of import, although supported within the language, is generally discouraged as it pollutes the namespace of the calling module and will cause already defined names to be overwritten in the case of name clashes.
Python also supports codice_28 as a way of providing an alias or alternative name for use by the calling module:
import numpy as np
a = np.arange(1000)
In XML, the XML namespace specification enables the names of elements and attributes in an XML document to be unique, similar to the role of namespaces in programming languages. Using XML namespaces, XML documents may contain element or attribute names from more than one XML vocabulary.
Namespaces were introduced into PHP from version 5.3 onwards. Naming collision of classes, functions and variables can be avoided.
In PHP, a namespace is defined with a namespace block.
namespace phpstar;
class FooBar
 public function foo(): void
 echo 'Hello world, from function foo';
 public function bar(): void
 echo 'Hello world, from function bar';
We can reference a PHP namespace with the following different ways:
include "phpstar/foobar.php";
$obj_foobar = new \phpstar\FooBar();
use phpstar\FooBar;
$obj_foobar = new FooBar();
use phpstar\FooBar as FB;
$obj_foobar = new FB();
$obj_foobar->foo();
$obj_foobar->bar();
Emulating namespaces.
In programming languages lacking language support for namespaces, namespaces can be emulated to some extent by using an identifier naming convention. For example, C libraries such as libpng often use a fixed prefix for all functions and variables that are part of their exposed interface. Libpng exposes identifiers such as:
 png_create_write_struct
 png_get_signature
 png_read_row
 png_set_invalid
This naming convention provides reasonable assurance that the identifiers are unique and can therefore be used in larger programs without naming collisions. Likewise, many packages originally written in Fortran (e.g., BLAS, LAPACK) reserve the first few letters of a function's name to indicate which group it belongs to.
This technique has several drawbacks:
There are several advantages: