Sweet. I need to give this a try and see if it works. Also another thing i wanted to mention is that i do not know if that will make a difference or something. Right now my main bottleneck in my iphone app is the asCContext::ExecuteNext function. I do not know if it will make a difference once i change my function from asCALL_GENERIC to asCALL_CDECL or asCALL_THISCALL

ExecuteNext is where all bytecode processing happens. If you do most of the code in scripts it is only natural that the application will spend the most time there.

It may not make a difference in performance to use asCALL_GENERIC or native calling conventions, but using native calling conventions has other advantages, e.g. less wrapper code, and easier maintainance.