Cody Boone Ferguson
f0de51a345
Although there were a few lines that I kind of looked over quickly, not evaluating the files in question, those seemed in good state anyway. Often that was binary files. In some cases for example input more information was given but not in all as it was not always clear what it should be and it was not always clear that it was necessary. Some typos were fixed as well. Rebuilt .entry.json and index.html files. A few other files were also modified with some minor fixes like 2006/toledo2/README.md for one example. In that case I believe some binary files were referenced as %%REPO_URL%% but that is incorrect. These files were edited before the index.html files were rebuilt so they should be fine. It should be noted that although I have gone through the entire manifest and it might be that issue #1933 can be closed there is still a chance that when I go through the web pages that I might come across a problem that I will fix at that time. This might or might not be needed but that will be determined later. Now might be a good time to run make www but I will worry about that later (it might or might not even do anything, depending on what was missed).
Nineteenth International Obfuscated C Code Contest
Standard IOCCC stuff
View the index.html web page for the given winning entry for information on how
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 IOCCC has a web site and now has a number of international mirrors. The primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
This year we included most of the information included by the submitters
in the README.md files (that were used to build the index.html web pages).
Read over the Makefile for compile/build issues. Your system may require
certain changes (add or remove a library, add or remove a #define).
Some ANSI C compilers are not quite as good as they should be. If yours is lacking, you may need to compile using gcc instead of your local compiler.
Remarks on some of the entries
There were some outstanding entries that did not win. Unfortunately some very good entries lost because they:
-
depended too much on non-portable side effects in expressions;
-
depended too much on a particular byte order;
-
required the use of a special script, data file or pseudo-machine language that was not supplied with the entry.
We hope the authors of some of those entries will fix and re-submit them for the next IOCCC.
We believe you will be impressed with this year's winning entries. The Best of Show is a fine example of (retro) obfuscation. But don't ignore the other entries! There are games, puzzles, puzzle solvers, simulators, emulators, calculators and graphical and audio tools.
This year a single person won three awards and another two awards! Many authors won for the first time this year. (Please note that judging is done completely anonymously. Be warned that we may disqualify entries that reveal the identity of the submitter).
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.