|
|
Ahh yes!! The trails and tribulations of typing in programs from magazines!! That bit of trivia sure brings back memories for me!! I had to go through the same thing on the Commodore 64 and the same thing happened!! Most of the time to distinguish between 0 and o is that the zero had a slash going right through it, so people wouldn't get confused. Programs started having checksums built in, which had a pre-determined total. If it didn't match, it would say so, and so it goes, LISTing the data statements to find the error!! Very frustrating and time consuming!!! I felt the same way like you did!! |
| An okay game that borrows a concept from Missile Command, in which you defend the city from attack. The enemy plane continually drops bombs until you lose your entire city (which can take a LONG time!). All you do is aim your crosshair to detonate the bomb out of harm's way. It's written in part machine language, but it's still a bit clunky to play. As another early game I typed in, I learned that if you mistype even one bit of code in the DATA statements (all those numbers to execute the machine language code) it causes the game to crash before it will even run! I remember spending hours and hours proofreading my typing before I finally caught one little obscure "O" that should have been a "0" (zero!). |
| | | |
| |
Issue 35 dated April 1983.
Missing original BASIC file! |
| | | | |