On Thursday 29 May 2008 08:45:26 Will Coleda wrote: > Even if there is disagreement on whether the opcode itself should be > removed, there appears to be consensus that the tests need to be > removed. We can always do that first to deal with the tickets relating > to that, and then discuss the merits of having the opcode in parrot > after that.
There are more than a few other opcodes which serve as examples. If people copy this particular one, they'll have at least one blatant bug. Let's remove it. -- c
