Cody Boone Ferguson
009e1b7522
The location of the link is in the About menu under the 'Contacting the IOCCC' and above 'Thanks for the help'. At first I had it at the very bottom, under 'IOCCC markdown guidelines', but it seemed better to have it closer to contacting the IOCCC. This is the same location in the no JavaScript menu (which, for those who do not know or forget, is not a requirement except for some screen sizes). The top level Makefile has a new 'security' rule. Updated make help. Typo fixes in make help. SECURITY.html has had a few updates as well: change the wording of entry code is unsupported (it now says 'ALL CODE IN ALL IOCCC ENTRIES IS UNSUPPORTED!!') and it now links to the mkiocccentry repo and how to report a possible security vulnerability in that repo; as that IS supported - and since there was reference to discussing security concerns is in SECURITY.html - even though the entries will not receive security updates - it seemed a good idea to have a link to report such security issues in the mkiocccentry repo. Perhaps the FAQ needs to be updated for this too.
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?