Jeff sent the following bits through the ether:
It runs strange code because it depends upon partially-deprecated code.
Try 'set P0[2], 1' and 'set I0,P0[-2]'...
OK, when will we get set P0[2], P2? Is it because the semantics aren't
defined yet? Do we copy or leave references? I really need
Josef Höök wrote:
i found some strange behaviour in perlarray.pmc
Consider this code:
new P0, .PerlArray, 2 # P0[2]
set P0, 2, 1 # P0[2] = 1
set P0, -4, 1 # P0[-4] = 1
# Above runs some strange code:
# ix += SELF-cache.int_val
# where
i found some strange behaviour in perlarray.pmc
Consider this code:
new P0, .PerlArray, 2 # P0[2]
set P0, 2, 1 # P0[2] = 1
set P0, -4, 1 # P0[-4] = 1
# Above runs some strange code:
# ix += SELF-cache.int_val
# where ix is our key
#
