On Mon, 8 Sep 2003, Piers Cawley wrote:
> Luke Palmer <[EMAIL PROTECTED]> writes:
> > Zellyn Hunter writes:
> >> So I take it the goal is to to teach parrot to understand z-machine
> >> opcodes, rather than simply writing a z-machine interpreter that
> >> runs on parrot, or rewriting inform to compile to parrot?
> >
> > I doubt it. I think a z-machine to parrot converter, making some of the
> > more complex ops sub calls or something, would be best. We need to work
> > with the z-machine bytecode directly, though, because many games are
> > distributed without source.
> >
> > And perhaps, once dynamic opcode loading is ready, those sub calls can
> > turn into real ops for speed. But that's not important at the moment:
> > the important thing (well, as important as z-machine can be :-) is to
> > get the translator working.
>
> Turning them into real ops might not be the right thing to do in the
> presence of JIT of course.
Nah, that's not an issue. The JIT has to be able to handle loadable op
libraries. It can TIL the unknown ops easily enough, and we can make sure
sufficient information is attached to the op libraries to allow real
JITting as well.
Dan
