
'ref' is alright.
It's a universally acknowledged standard abbreviation of 'reference'.
That would work.
'gen' is not, as it's unclear what it means.
'han' would not be acceptable either..
But this is nerd-jacking.

Too many projects; too much time
No, to be honest, it's not really a problem.
'ref' is alright.
It's a universally acknowledged standard abbreviation of 'reference'.
That would work.
'gen' is not, as it's unclear what it means.
'han' would not be acceptable either..
But this is nerd-jacking.
AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game
There is a new engine feature to support this. The generic handle type (for lack of a decision on the name) is registered as a value type but with a new flag asOBJ_ASHANDLE to allow the script to treat it as if it was a handle.
The dynamic casting is also supported with an new alternative function signature for the asBEHAVE_REF_CAST behaviour: 'void f(?&out)'. This will let the generic handle type receive the type id of the expected type, and return the appropriate pointer (or null if the cast is invalid).
The new engine features are already implemented in the SVN, though not yet documented.
AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game