At 9:45 PM -0700 7/8/02, John Porter wrote:
> > Dan wrote:
>> > 1) Dig through the perl source and find out all the opcodes.
>> > (pp.c and friends) Document the opcodes and what they do.
>> >
>> > 2) The same as #1, only for Python
>> > . . .
>> >
>> > Once we get these, the next task is to write an opcode library
>> > for them...
>
>I want to understand what the ultimate purpose of this is.
>
>I assume (but I'm open to correction) that it is *not* to simulate
>the vm of other language environments, so as to execute faithfully
>bytecode produced in those environments. (That is, taking object
>code from a python compiler (e.g.) and executing it in our own vm.)
Actually, that's one of the purposes.
>Perhaps the idea is to be able to run "foreign" source code by
>compiling to the parrot vm, appropriately extended with opcodes
>to make life easier for the compiler implementor.
That too.
>Or perhaps the point is to make sure we don't miss out on some cool
>operations that other languages have. :-)
That I'm less worried about, since the number of cool operations that
other VMs and languages has is fairly small, unfortunately.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
