Load(int_variable);
void Load(void *ref, int typeId)
{
// find name of ref, not type name
}
// script
void func()
{
int variable;
Load(variable);
assert( variable == 42 );
}
// C++
// Registered with signature "void Load( ? &out )"
void Load(void *ref, int typeId)
{
if( typeId == asTYPEID_INT32 )
{
*(int*)ref = 42;
}
}
// or with signature "void Load(int &out)"
void Load(int &var)
{
var = 42;
}
Is this intended to be some lightweight way for (limited) saving of the script's state? For that, you can check out the Serializer addon: http://www.angelcode...serializer.html
class Test
{
int a;
float b;
Test2 child; // this has its own Serialize() function
Serialization @Serialize()
{
Serialization @ser;
@ser = CreateSerialization(@this);
ser << a; // << operator is Load(?&out)
ser << b;
ser << @child;
return @ser;
}
}
Perhaps this can be of use: http://pastebin.com/bQ0j8YMV
It has some stuff specific to the game it is from, and requires some extra engine functions to be able to serialize floats. It does not know the name of the resource it tries to serialize though, so it relies on the order of << and >> calls.
engine->SetEngineProperty(asEP_ALLOW_UNSAFE_REFERENCSE, true);
I'm afraid it simply doesn't work that way. In order to guarantee that the reference sent to a function AngelScript will sometime have to send a reference to a temporary variable rather than to the real one, when there may be a change the real one is destroyed during the function call.
You can turn on unsafe references, which will let AngelScript send the reference to the real variable as an &inout reference. However, I cannot guarantee that this will allow you to find the name of the real variable in all instances.
To turn on unsafe referecences, the application should call:
engine->SetEngineProperty(asEP_ALLOW_UNSAFE_REFERENCSE, true);
Remember, a badly written script can crash the application if you turn this on.
came this far without using asEP_ALLOW_UNSAFE_REFERENCE, i am scared of it
