Namespaces can be used to group related functions and other entities together. Doing so avoids potential conflicts with other entities that happen to use the same name, but is otherwise unrelated.
Namespaces can be used in the application registered interface, as well as in the scripts.
Registering the interface with namespaces
To register a function, or other entity in a specific namespace, the application should first call the method SetDefaultNamespace to define the desired namespace. After that the registration follows the normal procedure as described in the chapter on registering the interface.
{
int r;
}
@ asCALL_CDECL
A cdecl function.
Definition angelscript.h:226
#define asFUNCTION(f)
Returns an asSFuncPtr representing the function specified by the name.
Definition angelscript.h:675
@ asOBJ_REF
A reference type.
Definition angelscript.h:250
The engine interface.
Definition angelscript.h:1092
virtual int RegisterObjectType(const char *obj, int byteSize, asDWORD flags)=0
Registers a new object type.
virtual int RegisterGlobalFunction(const char *declaration, const asSFuncPtr &funcPointer, asDWORD callConv, void *auxiliary=0)=0
Registers a global function.
virtual int SetDefaultNamespace(const char *nameSpace)=0
Sets the current default namespace for registrations and searches.
If desired nested namespaces can also be used by separating them with the scoping token, ::, e.g. SetDefaultNamespace("outer::inner");
Finding entities in namespaces
As namespaces allow multiple declarations with the same signature, it is necessary to specify in which namespace a search for an entity is to be done. This is also done with the SetDefaultNamespace method. This applies to both the engine and the module interfaces.
{
int r;
r = module->SetDefaultNamespace("myspace"); assert( r >= 0 );
assert( funcA == funcB );
}
The interface for a script function description.
Definition angelscript.h:3823
The interface to the script modules.
Definition angelscript.h:2218