op.c: avoid direct op_sibling access
authorDavid Mitchell <davem@iabyn.com>
Mon, 30 Mar 2015 14:53:07 +0000 (15:53 +0100)
committerDavid Mitchell <davem@iabyn.com>
Mon, 30 Mar 2015 14:53:07 +0000 (15:53 +0100)
commitcb74824085db788b8cbf6dbde3c1f1f39d978811
treeebad14198484a435144f85bb3543fe31a0e32422
parent4e0341d2ce817c9956f7f78e36bcaf8b764e18fc
op.c: avoid direct op_sibling access

Since the introduction of OpSIBLING(), op_sibling_splice() etc, a few
places in op.c have started directly accessing/manipulating op_sibling
again. Use the higher-level macros/functions instead.
op.c