Ah, bummer. I was hoping it would end up being something cooler. Like in the 80's, writing games for the Commodore 64... Where they kept the memory for the p

Ah, bummer. I was hoping it would end up being something cooler. Like in the 80's, writing games for the Commodore 64... Where they kept the memory for the program at a location shortly after where they kept the screen memory... So if you forgot to bounds-check the coordinates of the little guy you had running around on the screen, you could run him right off the bottom. Where he'd start overwriting random bits of memory. Until eventually he walked right over your source code. Which was being interpreted. Until, of course, the guy caught up with the current execution point. At which point, you hoped you had spent 10 minutes saving a copy of your code recently. Because listing your source you'd find it speckled with random special characters and changed values. Tire tracks from that little guy. And you learned that the first thing you do when implementing that joystick routine is to also implement bounds checking.