Dan Sugalski <[EMAIL PROTECTED]> wrote: > At 6:04 PM +0200 4/19/04, Leopold Toetsch wrote: >> >>I'm not sure if we need the two different get vtable methods though. At >>least there isn't any usage for these ;)
> Well, think of aggregates (where it's most likely to be used) That was the next question, you'd snipped away :) set Sx, Py assign Sx, Py don't access aggregates. The assign forms set Sx, Py[Iz] # implemented assign Sx, Py[Iz] # needed? new Sx, Py[Iz] # or even new Px, Py[Iz] # these 2? and the PMC variants (and different _keyed variants) are missing. All the assigned get can be done (or should at least) with an additional instruction, which could be a shallow clone. The set vs assign "set" instruction can't be emulated. I'm still in favour of keeping the opcode count as small as needed. Parrot's opcode dispatch is fast enough to deal with that. Cache misses due to huge opfiles are issues, which can't be delt with. The same idea holds for vtable size. leo
