Cody Boone Ferguson
af5482825c
The sections have been modified a fair amount. The Entries menu has been extended to have: Fixing entries, Updating author info, Thanks for the help. The first two were moved from FAQ and the last one from About. The rationale for these, in order: entries and authors have to do with entries and most of the help involves entries. It also has to do with website but in 'about' it does not seem the right place, unless maybe it is renamed to 'Credits' or something (I am not suggesting this one way or the other). This one is debatable but that was the rationale. The Status menu has been extended to have: Markdown guidelines and Security policy. The rationale is that the markdown guidelines are part of contest guidelines and the security policy is about the status of the entries and how if there are any security problems they will not be addressed (instead of about the IOCCC). The FAQ was extended to have: Compiling entries, Running entries, How to help. The reason to not have compiling and running entries under Entries is because this is 'how to' and also the menu was too long. How to help seems like a good idea under FAQ too (was in About). About was extended to have the new 'about.html' page (from about.md). This is a rare case where a new file is useful as it fits under 'About'. The menu now is: Home page, About the IOCCC, The Judges, Contact us. I was pondering the 'About [the IOCCC]' at the top and also naming it 'About us' but it seemed like a link to index.html was necessary and as for 'about us' it seemed less clear as to whether it was about the judges or the contest itself. The FAQ has been updated slightly for this. After further inspection the bin/index.html and the inc/index.html links were removed from the about section. With these changes, renaming an item or slight reordering notwithstanding, I believe that #2006 is probably in good shape.
Eighteenth 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 the entry 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.
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.
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).
Historical note:
The IOCCC has a website and now has a number of international mirrors. The primary website can be found at www.ioccc.org.
Historical update:
The IOCCC website once had a number of international mirrors. As of 2020 Dec 29, GitHub serves as the distributed server farm for the IOCCC winner repo that GitHub renders as Official IOCCC web site - www.ioccc.org.
Remarks on some of the entries
We believe you will be impressed with this year's winning entries.
In particular:
-
The Abuse of the rules - 2005/klausler used local dictionary data to get around the size limit.
-
The Most beauteous visuals - 2005/vince made clever use of
{}s and whitespace in their source code and during execution. -
The Most circuitous walk - 2005/vik entry is just amazing.
-
The Best game - 2005/toledo makes full use of its single function.
-
The Best emulator - 2005/sykes may allow you to reconnect to your first PET.
-
Our Best of Show - 2005/persano this year was simply (or non-simply :-) ) the best!
-
(And we need only mention (parenthetically speaking) that the Best use of parenthesis is self reproducing).
-
The Most sonorous output - 2005/jetro might
sound:-) like a good idea. -
The Best 2D puzzle - 2005/giljade takes editorial license with expressions as well as the with the vi editor.
-
The Most ambiguous language - 2005/chia entry is really a C program.
-
The Most superfluous output - 2005/boutines entry is simply Voronoi-lific!
-
Try not to have your sense of good coding offended by the Most discourteous interpreter - 2005/timwi entry.
-
The Best use of the www - 2005/mynx doesn't include those letters.
-
You will be puzzled by the Best 3D puzzle - 2005/anon entry; we are sure!
-
The Most ingenious puzzle solution - 2005/aidan might puzzle you more while it puzzles out some puzzles: all in a puzzling way! :-)
Remarks on some of the losing 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; and/or
-
depended too much on a particular byte order; and/or
-
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 resubmit them for the next IOCCC.
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.