Primitives

Primitives in AngelScript have direct matches in C++.

AngelScript	C++	Size (bits)
void	void	0
int8	signed char	8
int16	signed short	16
int	signed long (*)	32
int64	signed long long	64
uint8	unsigned char	8
uint16	unsigned short	16
uint	unsigned long (*)	32
uint64	unsigned long long	64
float	float	32
double	double	64
bool	bool	8 (**)

%*) If the target CPU is 32 bit, the C++ type long is 32 bit, but on 64 bit CPUs it is commonly 64 bit, but in AngelScript an int is always 32 bits.

%**) On 32 bit PowerPC platforms the bool type commonly have the size of 32 bit, when compiled on such platforms AngelScript also uses 32 bits for the bool type

Arrays

The AngelScript arrays are not directly matched by C++ arrays. The arrays are stored in an special object, accessed through the asIScriptArray interface. Thus you can normally not directly exchange a script with a C++ function expecting a C++ array, or vice versa. Nor can the application register C++ arrays as properties and expect AngelScript to be able to understand them.

It is however possible to override AngelScript's built-in array objects with application specified objects, on a per array type basis.

Object handles

The AngelScript object handles are reference counted pointers to objects. This means that for object handles to work, the object must have some way of counting references, for example an AddRef/Release method pair.

When AngelScript passes an object handle by value to a function it increases the reference count to count for the argument instance, thus the function is responsible for releasing the reference once it is finished with it. In the same manner AngelScript expects any handle returned from a function to already have the reference accounted for.

However, when registering functions/methods with AngelScript the application can tell the library that it should automatically take care of releasing the handle references once a function return, likewise for returned handles. This is done by adding a + sign to the @ type modifier. When doing this an object handle can be safely passed to a C++ function that expects a normal pointer, but don't release it afterwards.

See Also: Object handles

Parameter references

Because AngelScript needs to guarantee validity of pointers at all times, it doesn't always pass references to the true object to the function parameter. Instead it creates a copy of the object, whose reference is passed to the function, and if the reference is marked to return a value, the clone is copied back to the original object (if it still exists) once the function returns.

Because of this, AngelScript's parameter references are mostly compatible with C++ references, or pointers, except that the address normally shouldn't be stored for later use, since the object may be destroyed once the function returns.

If it is necessary to store the address of the object, then object handles should be used instead.

Reference	Description
&in	A copy of the value is always taken and the reference to the copy is passed to the function. For script functions this is not useful, but it is maintained for compatibility with application registered functions.
const &in	If the life time of the value can be guaranteed to be valid during the execution of the function, the reference to the true object is passed to the function, otherwise a copy is made.
&out	A reference to an unitialized value is passed to the function. When the function returns the value is copied to the true reference. The argument expression is evaluated only after the function call. This is the best way to have functions return multiple values.
const &out	Useless as the function wouldn't be able to modify the value.
&inout	The true reference is always passed to the function. If the life time of the value cannot be guaranteed, a compile time error is generated and the script writer will have to copy the value to a local variable first. Objects that support object handles are best suitable for this type as they can always be guaranteed.
const &inout	The reference cannot be changed by the function.

If the application wants parameter references that work like they do in C++, then the engine property asEP_ALLOW_UNSAFE_REFERENCES can be set. When this is done, the parameter references can be declared without the in, out, or inout. The parameter references declared without any of the keywords will always pass the address to the original value, and will not have any restrictions to the expressions that can be used. The parameter references with the in and out keywords will still work like before, but the references with the inout keyword will have the restrictions removed so that they work just like normal C++ references.

The application writer and script writer has to be aware that it is possible to write scripts that access invalid references when the library is compiled in this mode, just like it is possible to do so in C++.