Landon Curt Noll
dbf6921b3a
Updated 1337 hacker rulz to version 7. Added `1337.mk` to contain the updated 1337 hacker rulz (v7). We use an optional include of `1337.mk` (or `../1337.mk`, or `../../1337.mk`) to include the 1337 hacker rulz. Changed `make deep_magic` to `make more_magic`. Changed `bin/tar-entry.sh` VERSION from "1.3.7 2024-07-22" to "1.3.8 2024-07-23". Changed `bin/tar-year.sh` VERSION from "1.2.5 2024-07-22" to "1.2.6 2024-07-23". Add `make new_entry` to `YYYY/Makefile` and `template/Makefile.year`. Change `make new_year` to use `sort -n -u`. Made minor debug message fixes to `bin/new-year.sh`. Changed `bin/new-year.sh` VERSION from "1.3 2024-07-23" to "1.3.1 2024-07-23". Improved `bin/add-dir.sh` to update `YYYY/Makefile` with the new entry directory name. Changed `bin/add-dir.sh` VERSION from "1.0 2024-07-21" to "1.1 2024-07-23". Performed `make www` to accomplish the above and to test under macOS.
Third International Obfuscated C Code Contest
View the index.html web page for the given winning entry for information on how
to compile it and how to run the winning program. Look at the winning source
and try to figure how it does what it does! You may then wish to look at the
Author's remarks for even more details.
The rules for 1986 suggested categories due to the success of the 1985 judging method. The maximum size was increased from 512 to 1024 bytes. Larry Bassel joined as the second official judge.
A poll was taken for the worst code for
BSD and System
V program. The Bourne
Shell (/bin/sh) won for both
systems. The BSD finger
program took third place.
Rules and results were posted to net.lang.c and net.unix-wizards. Micro/Systems Journal started regular publishing of the winning entries. The practice of making first announcement of the winning entries at the Summer USENIX BOF (Birds of a Feather) started this year. A notice was posted to net.announce.
Final Comments
IMPORTANT NOTE: See contact.html for up to date contact details as well as details on how to provide fixes to any of the entries. See also the IOCCC FAQ for additional information on the IOCCC.