RE: [Emerson-general] Rough Instruction Set List

[Lucas M. <luc...@ro...>]

That looks good but why do we need a new class opcode? Didn't we decide that
metadata would describe types not code itself. Also we don't need two call
opcodes, if we treat a class as an instance of a metaclass that is
instantiated when the class definition is loaded, then we only need a
non-static call opcode, you call it from a different thing. Also, can't we
just make arrays objects instead of having a special case?, plus you
shouldn't be able to mess with threading. It should be completely automatic.
If it's not, then someone could, for example, purposely leave out lock
opcodes in hand coded asm to cause a data corruption attack. 

As for adding opcodes, we need assignment, flat function calls, and a return

opcode at least.

-Lucas