Brent -- > ....but how do I use an additional .ops file? I'd like to statically > link it in and use it alongside core.ops, but I can't figure it out. > The assembler can't find the opcodes, even after I run ops2pm. Is there > some magical command-line switch I'm not activating or something?
This is a great question. The answer is that until we get dynamic loading working its not going to happen. You need a unified opcode list for the interpreter, which I suppose you could create by writing some throwaway code in the interpreter, hardcoding the scans of the particular oplibs you are merging. That code won't be *totally* throwaway because its the same code we need once we have dynamic loading. Now you know why I begged the question by committing some platform- specific dynamic loading stuff the other day. I'm very eager to get this stuff working, but we can't do it until we've got that worked out. I've got dynamic loading working here, and the next step is to dynamically load two oplibs and merge them to create the customized oplib for the bytecode we are executing. As for Simon's comment about getting the assembler to work: I haven't even tried that. If it works, its not on purpose :) Regards, -- Gregor
