info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Time for permanent opcode numbers
4 views
Skip to first unread message
Dan Sugalski
Apr 15, 2003, 3:02:37 PM4/15/03
to perl6-i...@perl.org
Okay, the core opcode set for parrot, at least a good part of it, is
fixed and hasn't changed in ages, even factoring out the quiet
periods. (It's not like there's been much of a semantic change to
jmp) I think, then, it's time to start assigning permanent opcode
numbers to some of the opcodes. We can let a bunch float, still, but
it'd make the native bytecode tests fail less often every time
someone goes and adds a few new opcodes to the set...
--
Dan
fixed and hasn't changed in ages, even factoring out the quiet
periods. (It's not like there's been much of a semantic change to
jmp) I think, then, it's time to start assigning permanent opcode
numbers to some of the opcodes. We can let a bunch float, still, but
it'd make the native bytecode tests fail less often every time
someone goes and adds a few new opcodes to the set...
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk
0 new messages