....whose engagement transmits successive motive force to a corresponding wheel or gear.

More info here.

Yay! Sith2!

So does this mean we can set char strings as flex's and it will print in JK or what?

Flexes are the Babylonian whores of the COG symbol world. In my implementation you can assign virtually anything to them; no type checking is done for assignment, however types are checked for other operations if the flex is an L-value and has an internal type.

JK Datamaster implies that you can already assign string literals to flexes, although you might not be able to do them in the symbols section.

Hay, compile a Win32 version (or let someone else). >_>

UPDATE: A Win32 version of the COG VM is available now. See this thread for more details.

Please excuse my ignorance when I ask, can you give an example of what we can use this for in JK? I gather something about adding new verbs, but can you give an example? Thank you.

Sigh

Sorry, I still don't get it. By example, I meant pratical use in JK that expands on a pre-existing system or feature of the game. I can't determine this from looking at lines of code. I'm a graphics junky, not a code junky. The example you gave looks no different to me then any other cog I've seen written in the cog forum.

I guess I could boil it down to one example question for you.

Will this allow JK editors to add, say, the new verbs introduced in MotS or some of the vehicle cog verbs introduced in that Indiana Jones games?

No, this will not allow you to add new verbs to the existing JK engine.

This is a brand new COG Virtual Machine. It allows you to execute COG scripts - in fact, this is one of 3 programs in the entire universe that can execute them. The other 2 were made by LEC, one of which we will never have access to. This doesn't mean a whole lot now, but it opens up the serious possibility of creating a brand new engine that can play JK levels.

Jon`C has written the framework for a cog parser and interpreter, like JK uses. It is intended to be used in, for example, Jon`C's Sith engine (read: JK) clone, which will need support for cog.

It cannot be used in the existing JK or MotS engines.

[Edit: Bah, he hadn't posted when I was typing this. :(]

And a minor correction: It isn't an interpreter, it's an honest-to-god compiler and virtual machine. If I wanted to I could make the compile target x86 (although that would be disgusting overkill).

I have no idea what's goin' on...

/Towlie voice

So.... then coggers will now have ULTIMATE POWER and be able to bend the restrictive laws of the JK MATRIX??!

:O ooooh right

Ah, okay, that makes a lot more sense now. Basically, this is a setup for when the "JK clone" is completed, we can easily port all of the existing JK levels and mods into the clone without worrying about silly covertions that end up screwing the file up....cool. Good job!

Someone told me you were working on a JK clone - I think it was in the JKhub IRC room - but I didn't expect you to work on cog first! I've been fiddling with a sith clone, though I certainly had no plans to write my own compiler and VM. I was going to use AngelScript for that ([url]www.angelcode.com[/url]) Maybe it's time we collaborated?

Nice work Jon`C!

Dear god. I cannot imagine the amount of energy that would be released in such a cosmic collision of egos. It would be like two galaxies combining then all the stars going supernova at the same time.

Eh, not really. I'm not as much of an ******* once you prove you are worthy of my attention, and Jon'C has done that and more. He's certainly a competent programmer, and I'm sure we'd discover we have different areas of speciality.
On the other hand, I really don't like the idea of just cloning the sith engine straight out. Here are some reasons why.
-The engine would be limited by JED. Naturally, JED would be the editor at first, but it would have to be replaced if we ever wanted to do anything with the engine besides JK. First, you need JK to run JED. Second, JED is limited to working with JK resources. We do not have access to the JED source, and if we did, I doubt making any substantial change would be trivial.
-The cog file layout is hideous. I'd want to leave that behind, and use a real functional language instead.
-Mat files suck. I'd want support for, atleast, tga; but JED can't load them.
-Legal issues. Yes; if our engine actually could load a JK gob and play the level it would be illegal. The JK liscense says that any levels created for JK become the property of LEC. Therefore, we would have to do something like JED does, and only run if the JK cd is in.