Landon Curt Noll
4ee4c731f7
While not strictly necessary, replacing the two ASCII tab characters in the markdown copyright comment makes it easier to detect problematic TAB indentation within markdown files. After this commit, only 90 markdown files have leading ASCII TAB characters. And again, while not strictly necessary, we can consider running expand on those 90 markdown files to see what effect that might have on the HTML files they produce. Replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters (the default action of the `expand(1)` tool) might have an negative effect on some HTML formatting where **hack-a-round** formatting was attempted to fix broken indentation caused by problematic ASCII TAB characters. Think of this as a baseline for evaluating leading TAB characters within markdown files. TODO: Consider either using `expand(1)` to replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters AND/OR modifying the appropriate `bin` tool to convert leading ASCII TAB characters into multiples of 8 ASCII SPACE characters.
2.2 KiB
To build:
make all
To use:
./heathbar num num
where num is a non-negative number.
Try:
./try.sh
Judges' remarks:
The main reason we liked this entry was mainly because the main effect of the source was self documenting! :-)
Author's remarks:
Run this program with two non-negative integer arguments
(e.g. ./heathbar 1234 999).
My goal was to create the fastest possible C program. To that end, I made three critical observations:
- If there's one thing computers are good at, it's math.
- Simple operations take less time than complicated ones.
- Every C program seems to contain the word
main.
Based on #1, I knew that the Fastest Program had to be one that
performed addition. From #2, I reasoned that it ought to directly
manipulate the bits, rather than wasting time dealing with bloated,
high-level, fuzzy-logic, artificial-intelligence, neural-net,
client-server, object-oriented abstractions like the C language "+"
operator. And it was obvious from #3 that the program should
resemble, as closely as possible, a long sequence of the familiar
word main repeated over and over, so the computer would be
comfortable running the program and wouldn't get distracted dealing
with unfamiliar variable names.
Also, I've looked at some past winning entries of your contest, and if you don't mind a little constructive criticism, some of them are kind-of hard to figure out. I didn't want my program to fall into the same trap, so I went out of my way to write self-documenting code. Anyone who so much as glances at my program will immediately see that it adds two 16-bit unsigned integers by streaming their bits through a simulated cascade of hardware adders. I hope my diligent effort to write especially clear code gets me extra points!
P.S. What does "obfuscated" mean?