Back in to this topic again.

I recompile scripts like this,

Save Stuff (Events, Object properties, etc..)
DiscardModule
reRead Changed files
CreateModule
Load Stuff

this method partially works but has some real drawbacks.
- everytime new classes/ events introduced i go back to save/load methods
- forces script writer to have strict rules if recompile to be done

this is very tedious as you imagine. it kills my motivation to add new events and c++ objects to scripts.

i know angelscript is not designed to be recompiled at runtime,
but i should still ask since i am very inexperienced about the engine. might be missing something.

is it somehow possible to not call destructors and disable destruction of globals and refcounted objects upon module recompilation?

thanks.

There is no way to avoid the destruction of the objects during the recompilation. You can serialize the objects so they can be reconstructed after the compilation, but the original objects will be destroyed.

There is no way to avoid the destruction of the objects during the recompilation. You can serialize the objects so they can be reconstructed after the compilation, but the original objects will be destroyed.

ok.

is it possible to compile a dummy module and copy its type definitions/functions to the actual module one by one, update if already exists?

Unfortunately not.

then i will close the chapter of "dynamic compilation".
man gotta know his limits.

thank you.

It would be a useful feature, and if I can figure out a working solution it is definitely something I would like to add.

It would be a useful feature, and if I can figure out a working solution it is definitely something I would like to add.

thank you for consideration

angelscript is the most feature rich scripting language i have used. and it gets better and better