Hi I think the ability of passing arguments to the constructor wrapper class of the regeistered objects (class) is a good addition, that way we can register class factories. CObject* _objectCosntructor(int type, CObject* thisPointer) { return new(thisPointer) registeredObject(type); } i will try to modify the library in the next days (unless there is a specific limitation in the anglescript library to this ctor method), or if i dont have time, i will do it via a preprocesor , anyway, i let you know that passing arguments to constructors can be a good feature to add About the JIT compilation (to improve the execution speed), is there any study going on to implement JIT compilation to angelscript? Here are some links to JIT compilers for bytecode executed on VMs http://www.southern-storm.com.au/libjit.html "The libjit library implements Just-In-Time compilation functionality. Unlike other JIT's, this one is designed to be independent of any particular virtual machine bytecode format or language. The hope is that Free Software projects can get a leg-up on proprietry VM vendors by using this library rather than spending large amounts of time writing their own JIT from scratch" http://softwire.sourceforge.net/ "SoftWire is a run-time x86 assembler, written in C++. It can be used as a JIT compiler back-end for scripting languages, or for dynamic code generation of optimized inner loops." great library you have here (angelScript), im testing it right now, and so far its very good, (implementing in a game framework), but im a little concerned about the speed, im targeting at controlling the game runtime via scripts, so they will be executed every frame and for the game logic, not GUIS or simple functionality Lioric

Hi

i did a little more research and there are very confronted opinions about jit and bytecode copmpiled scripts

but here there is a scripting library that has as addon a jit compiler with source code

http://www.compuphase.com/small.htm

Lioric

Hi WitchLord,

Im happy to see that you will implement these features in the angelscript future

If modifying the library to pass arguments to constructors doent tak more than a day or a couple of days, i will do it , but if not (the project is a little overtime by now), i will go for the proprocessor way

parse the script for the object declaration:

CObject* _obj = new "sphere"; ( or CObject _obj(OBJECT_TYPE_SPHERE); )

add the object types to a deque of types in the order they are declarated
replace the script lines where the object are declarated with the object pointer declaration only (CObject* _obj;)
compile the script, and whe the registered constructor is called do construct the derived objects

CObject* _objectConstructor(CObject* thisPointer) {
ObjectType type = type_deque.front();
type_deque.pop_front();

return new(thisPointer) registeredObjectClass(type);
}

Im still concerned about the speed of the library (or to be fair with the speed of bytecode execution in general), i know that the new unreal engine uses bytecode scripts (probably a highly optimized compiler and vm).
But as my project is a game framework, the user will have control on the execution or what the game does, so the more speed i can give the end users, the less complains and messages to my tech support guys

I want to let you know that i really want to use your library, i have the angelscript homepage bookmarked for about 6 months by now, and finally the project is in the "implement scripting feature because its a good feature and because the competition has it and its very fast" stage, but overall because angelscript its very good coded and have good features, but i still have some scripting libraries left to try.

About the speed, i saw on the raptorentertaiment page some screenshots, and they report a very low fps, 10.40 in the frist screenshot i saw, and 17.some in the second, but im sure its because they are debug screenshots

best regards,

Lioric