I’m actually having trouble thinking of a time when you’d want several script threads. I guess just for totally unrelated tasks or something… Oh, and bear in mind that multiple processors/cores is only going to get more common. So although simulating threads for script sounds fine you might want some real ones in the engine, when the time comes.

That’s exact what I ment about threads. I hope it’s okay to use your wording?

Yeah, I’m not up to do the low level assembly - maybe later. I don’t want to support a large number of combinations of processor and operating system types. Standard C++ is the way I’m going for the moment.

The idea with C++ calling voodoo is that each method (or groups of methods - it doesn’t matter) has a voodoo method object. Each voodoo method object has a constant pool and a link pool, these are objects and constants that the virtual machine keeps track of and relinks when necessary. So the C++ calling method would access these objects in a similar way to voodoo bytecode, by offsets (or a hashmap or whatever). So when a C++ method wants to use a voodoo integer it just uses the one in the constant pool that it registered earlier. This way everything is linked together still and it will be faster than a lookup every method call. Most of the calls will be from the code that makes up a voodoo object anyway, all in the way I’m going to use voodoo - as the complete controller of the game.

About the network proxy objects, you might find this page (I really hope links like that work) on unreal’s networking architechture interesting. I know I did. Unreal’s networking is done from script too, so it couldn’t really be more relevant.

I’m not sure quite what you mean by: “Threads are implemented in a hardware independant manner which means that there can be more executing at once without swamping resources.”
Do you mean you’ll simulate threads by swapping between bits of script rather than creating OS based threads?

Random thought, you could do some hard core assembly and implement you’re own threading, leaving the OS in the dark. On x86 it only takes one instruction to load or save the processor state… Or you could shoot me for turning to the low level dark side. In fact that sounds like a better idea. Yeah.

About calling from c++, what sort of interface do you have in mind? You say voodoo is purely OO, which might make it a little more difficult.

Plus it sounds really cool saying, yeah - I made my own programming language from the ground up.

Thanks a lot for the encouraging words.

I dont know anything about this stuff, but I’m using a one-man-made language-compiler-gfx engine called BlitzMax, which is really kickass.

Which proves it’s possible, but it’s really hard I guess to make something you will actually want to use. (that guy has about 10 years experience doing this stuff and does it full time)

Well good luck anyway