Landon Curt Noll
96e0f2b966
A number of rules have been moved from entry `Makefile`s into the `1337.mk` include file to make it easier for these common rules to be updated or modified globally (by modifying the `1337.mk` include file). The entry level `Makefile`s are now similar in form to the /Makefile.example](https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example) file from the other repo. The following make rules were moved into the `1337.mk` include file: - `make indent.c` - `make install` - `make diff_orig_prog` - `make diff_prog_orig` - `make diff_alt_prog` - `make diff_prog_alt` This simplifies the entry level `Makefile`s so that they mostly reflect the specifics of the particular entry. Mentioned in FAQ 4.2, that the make diff rules are in the `1337.mk` include file. Fixed invalid TAB character in `faq.md`. Removed `make clean` directives that removed `indent.c`. This file is now removed via `make indent_clean`, a clean rule that also removes `indent.c`. Removed `make clobber` directives that removed sandwich, This file is now removed via `make indent_clobber`, a clean rule that also removes `sandwich`. Added `make indent_clean` and `make indent_clobber` rules into the top level `Makefile` and the year level `YYYY/Makefile`. Performed `make quick_www` to accomplish the above and to test under macOS.
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?