Log In  

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)

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.

P#76883 2020-05-19 08:55

[Please log in to post a comment]

Follow Lexaloffle:        
Generated 2021-06-15 19:51:35 | 0.007s | Q:7