The opcodes are pretty powerful at the higher level controlling whole threads. I like to think it's FORTH-ish but without the stack management.
(Ok, I know Forth, everyone point and laugh at me now...)
Only if you really want us too!
I would have to look at the instruction flow. Likely its some strange OOP language. I doubt it's like smalltalk though since it had huge fees associated with it.
I'm guessing the math fuctions were probably picked by thier context by the compiler. (PLUS vs PLUS2) I also assume they has some header file to keep track of the globals.
Maybe depends on how the language worked. If for example it uses object pascals
unitization system, this just says 'I need the definitions of this module'. It's does not use a header file though it reads the compiled object file instead of parsing yet another file.
I suppose one should ponder what the script language looked like, based on the opcodes left by it and there organization.
Heck we could just wait until FF8 to work on that though. Since we are utterly clueless at the moment.
All we know is it supports coroutines (IE threads), Obviously globals, Possibly locals, and possibly object oriented data organization.
If the character under the user control is an object a lot of the scripting is simplified in a way.
The problem I have right now is my script dumper (Actually, it's Kero's) barely parses. It loses track of how many bytes to jump back to jump forwards. It also have very little concept of "pass by value" addressing. It's kind of a pain.
Well I suppose you could whip up your own ... and after a few months resume?
I'm just a little too lazy to make a script dumper myself.... and with Qhimm having one "somewhere" isn't exactly modivating me to crack open the Ruby to write my own. 
But I'll work through some script dumps tonight. I'll document what I can...
LOL
I suppose this is where things be then?
Anyhow back to finishing what I started.
Cyb
