Opcode arg count mismatch in PL/Parrot

[NotFound]

> Does anybody know what is going on? Any help would be appreciated.
> Just verified this with an installed version of r47098.

I think the problem lies in the dynamic opcode loading, Since we've
made dynamic a lot of opcodes, the problem manifest now much more
frequently, When load_bytecode a pbc that uses some dynops from other
pbc that uses some others, the opcode numbers get confused.

-- 
Salu2