Avoid using OP_NAME() in unimplemented_op(), as it won't give useful strings.
authorNicholas Clark <nick@ccl4.org>
Fri, 31 Dec 2010 16:20:11 +0000 (16:20 +0000)
committerNicholas Clark <nick@ccl4.org>
Fri, 31 Dec 2010 16:32:57 +0000 (16:32 +0000)
commit361ed549eb6ef15e68e6bb16e020f11b7a29ebb2
treeea897942cd1b865b1a4e9c2338f01b94f775fd93
parent4861580b3001ab81922a8c1f978ed071012baca4
Avoid using OP_NAME() in unimplemented_op(), as it won't give useful strings.

Using OP_NAME() isn't going to be helpful here. Firstly, it doesn't cope
with out of range op numbers - it only "special" cases op_custom.  Secondly,
as the three ops we "panic" on are padmy, mapstart and custom, if we get
here for a custom op then that means that the custom op didn't have an
implementation. Given that OP_NAME() looks up the custom op by its pp_addr,
likely it will return NULL, unless someone (unhelpfully) registers
&PL_unimplemented_op as the address of their custom op.  NULL doesn't
generate a useful error message. "custom" does. */
pp.c