First some background: as a lot of other people too I'm currently adding script support to my game project. I first used lua and luaBind but got more and more problems with that. So I downloaded angelscript and did some tests with it. Two questions: First: static methods I've got a simple test class like that: class A { static void StaticTest( const float pParam) { cout << "StaticTest: " << pParam << endl;} } I tried to register this static method as follows engine->RegisterObjectMethod( "A", "void StaticTest( const float)", asFUNCTION( A::StaticTest), asCALL_CDECL); but I get -7 (asNOT_SUPPORTED) as return value. So I tried to register this method at least as a global function engine->RegisterGlobalFunction( "void StaticTest( const float)", asFUNCTION( A::StaticTest), asCALL_CDECL); This registrations went fine but when I call this function from a script like this ExecuteScriptString( "StaticTest( 5.0f);"); not "5.0f" get's printed but it prints some long number (1084227584) which could be the this-pointer as an integer or something but is surely not the 5.0f I gave in. :) So what do I do wrong? And is there actually any possibility to register static class methods? -------------------- Second: problems with object pointers in scripts Consider some simple object factory and some simple object on the C++-side class SomeObjectFactory { [...] OneObject *CreateOneObject( ...) { ... } OneObject *GetObjectByName( const char *....) { [...] if( object_found) return object; else return NULL; } [...] } class OneObject { // reference counting only needed for script support void AddRef() {..} void Release() {...} const int SomeMethod() { return 5; } } On the script side: void AngelTest() { OneObject @obj = objectFactory.GetObjectByName( ...); if( obj != null) print( obj.SomeMethod()); } My problem is that I can't really see the reason why I must bloat all my classes with i.e. reference counting just to be able to use object handles on the script side. Isn't there any way to register my classes and to be able to work with object pointers on the script side without been forced to add reference counting? On the C++ side I take care of all the memory and object managment. I register everything so that OneObject can't be instanciated on the script side (registering objects with size 0). On the script side I just want to retrieve a pointer or NULL from the some C++ object factory and call some methods on the retrieved pointer. Well, pretty much a standard scenario, as you can see. The project I want to add scripting support to is rather large. So, as you might agree, adding reference counting (and maybe other things) to probably some hundred classes is surely not a solution for me. Is there a way around? I could write a template class which add's fake reference counting to any class, but I would like to avoid such measures if I can. Thanks for your time. Bye, Stefan.

Thanks for your explainations.

@static methods:
It's alright for me to register static functions as globals on the script side. I'm was just a bit sad about loosing the class scope/namespace, as that will surely lead to problems when there is more than one class with equally named static functions.

The reason for why I didn't get the float parameter I gave in is still unknown. I got in contact with Andreas so there will surely be a solution soon.


@reference couting:
Thanks for the template helper, looks useful.

I don't use smart pointers. I just take care of all the objects on the C++ side myself and I wondered why I have to register reference counting behaviour for objects which only exist on the script side as pointers or references (Handles) to objects. AS cannot rely on the reference counting as one is allowed to register dummy functions which don't do anything. My classes on the C++ side don't use reference counting, too.

I'm just wondering why I have to add so much stuff to my classes to use them on the script side for no apparent reason.

Well, I guess I have to live with that. It's not that big problem. :)

Thanks for your help.

Bye, Stefan.

What you can do to make it easier to add references, etc, is 1: inherit from a "Referenced" base class or 2, create a macro: DECLARE_IS_REFERENCEABLE().