[This is part 3 of the Writing Compilers series]
In high school I was an avid logic-puzzle solver, voraciously scouring the school and public library for new conquests. Along the way, I came across the “Mathematical Recreations” column in Scientific American. In particular, one article described “Core War,” a game where programs written by the players fought against each other in the memory of a virtual computer system. The winner was the program that caused the enemy to execute an illegal instruction.
The language of Core War is called Redcode, a simplified version of assembly language, and served as my introduction to many advanced concepts including registers and addressing modes, data vs. text segments, multi-threaded concurrency, defensive programming (literally!), virtual machines, and low-level debuggers. Truly, Core War was one of my foundational learning experiences!
I played the game for many years, contributing several articles to The Core War Newsletter (Vol 6 issues 2 & 3). The evolution of the language itself and the strategies involved in winning offered a continuous stream of intellectual and technical challenges. The apex of my Core War experience was writing a genetic algorithm to evolve warriors and pitting them against the latest-and-greatest warriors in the competitive hills.
Read More »
[This is part 2 of the Writing Compilers series]
The first ‘real’ language I tried learning was C. I had written extensively in BASIC throughout middle school, but never felt satisfied. It was too far removed from the hardware, too distant from the ‘true’ nature of the computer. C, on the other hand, seemed like a backdoor left open by some inattentive operator, with direct access to the control room.
I purchased a copy of “C – The Complete Reference” at a local bookstore, my first technical manual.
I believed the tome to be an ancient wizard’s codex containing all the knowledge needed to master C programming, and by extension the computer. I was unprepared for the depth of technical background and vocabulary required to put the book to use. The arcane, almost alien, language consisted of symbols jumbled in random order, indirect references to objects of unknown identity lost in translation to the English language.
Simply put, “C – The Complete Reference” was not a good introductory programming guide for middle school students.
I turned instead to Pascal, the ‘native’ language for my new computer – a Macintosh 512K aka “fat mac.” Apple’s API toolbox, the ROM itself, used the Pascal calling conventions. It would be some years before I returned to C, this time with little doubt I could master it.
Read More »
[This is part 1 of the Writing Compilers series]
I’ve been a programmer for almost my entire life – I still remember my Dad letting us play games on his early home computer. I was in first grade in the early-80s and “home computer” was an infrequent term. I was playing a game not unlike Missile Command, becoming frustrated that the enemies were too hard to shoot.
I wanted them to move slower. More specifically, I wanted my Dad to make them move slower. In the naivety of youth this seemed trivial, something my all-powerful father could certainly accomplish with just a wave of his hand. Of course I was distraught to discover that he could not alter the game’s behavior.
This led to a different kind of frustration, one which launched my career and still drives me today; HOW do those little dots move around in the first place? What controls them, and how can *I* become their master?
Read More »