So my only way forward was to sit in my bedroom and try to puzzle out the language based on my own guesses and whatever truths could be gleaned from the three-line code snippets scattered throughout the book.<\/p>\n
So I wound up with some gaps in my knowledge. Specifically, I didn’t know you could make your own functions. This is a hilarious thing to not know. A C program might look like this:<\/p>\n
\r\nvoid DoAwesomeThing ()\r\n{\r\n be awesome here; \r\n}\r\n \r\nvoid DoNeatThing ()\r\n{\r\n do some stuff;\r\n DoAwesomeThing ();\r\n}\r\n \r\nvoid main ()\r\n{\r\n do some stuff;\r\n DoNeatThing ()\r\n do some more stuff;\r\n DoNeatThing ()\r\n do still more stuff;\r\n DoNeatThing ()\r\n}\r\n<\/code><\/pre>\nBut if you don’t use functions – if you can’t (or don’t know how to) make DoAwesomeThing or DoNeatThing – then the program will turn into this:<\/p>\n
\r\nvoid main ()\r\n{\r\n do some stuff;\r\n {\r\n do some stuff;\r\n {\r\n be awesome here; \r\n }\r\n }\r\n do some more stuff;\r\n {\r\n do some stuff;\r\n {\r\n be awesome here; \r\n }\r\n }\r\n do still more stuff;\r\n {\r\n do some stuff;\r\n {\r\n be awesome here; \r\n }\r\n }\r\n}\r\n<\/code><\/pre>\nIf you find a bug in awesome thing, then you need to fix it in three different places. Copy & paste errors will propagate and the code gradually becomes an unreadable mess. Doing things this way basically defeats the most important features of the language. (I did things this way because I was trying to map my knowledge to C to my knowledge of Basic.)<\/p>\n
Most programmers will look at the above code and get all twitchy. It’s just so perfectly wrong<\/em>.<\/p>\nNever one to settle for small, reasonable goals, I decided that the best project after Hello World<\/a> was a full-featured graphical version of Tetris. <\/p>\nI wrote Tetris without a single function call. The entirety of the program was contained within main (). Start screen, the game loop, user input, line removal, scoring, increasing levels of difficulty, game over, high score list. Everything. All in main (). I cannot stress how convoluted this was. The code indenting was so deep that if you scrolled halfway down the (terrifyingly long) page, you would see nothing but blank space. The line indents were all the way off the right side of the screen. You had to scroll a full page width horizontally in order to see the code. <\/p>\n
I finally got my hands on real C code and learned how things are supposed to work. I wrote and re-wrote Tetris a few times over the next few years. I had a friend who would put the new versions up on a BBS<\/a> for me. When you exited the game, it printed out my real, actual home address and invited you to send a postcard. (I got three. Furthest away was from Japan. I was so excited. I communicated with someone in Japan!<\/em> I’m sure I do that every single day now.)<\/p>\nThe program and the source vanished ages ago in one of my early computer migrations. Shame. I would pay good money to see the no-function version of the Tetris source again, if only to gape at the horrifying awfulness of the thing.<\/p>\n
On a whim, I Googled around to see if it had made the jump from BBS to internet. It did:<\/p>\n
<\/td><\/tr><\/table><\/p>\nThat’s a 16 color graphics mode. I made it look like it had more colors by using dithering. (I was SO proud of figuring that out. Wrote a whole bunch of code to do smooth dithered fades. Spent ages on it, experimenting and looking for ways to make the blend as natural as possible. But the whole system was obsolete before I wrote the first line of code. 256 color mode was all the rage and 16 bit color mode was on the horizon.)<\/p>\n
The program was more future proof than many. It still runs on my computer and is still playable. The only thing that breaks is that there was no CPU throttle on the PC speaker based sound effects, so the sounds are reduced to almost completely inaudible millisecond long blips. (Sounds work right under Dosbox<\/a>, though.)<\/p>\n