Not sure if it is really a bug, but poking at the 8 bytes starting at 0x5f4c then immediately peeking will discard the two highest bits:
> p=0x5f4c poke(p,255) print(@p) 63 |
I know this is a special area and the memory is modified by the virtual hardware between frames, but no other location discards bits like that.
[Please log in to post a comment]