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.
Sixteenth 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.
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.
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
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 obfuscation. But don't ignore the other entries! There are games, programs that speak, ones that compile code and one that might run binaries you already have.
The Best abuse of the rules is technically allowed by the rules. This year we awarded it again, but don't assume you can get away with using the same technique next time ... :-)
This year there were several repeat authors. This is understating the achievement a little - one person has won 8 times before! (Please note that judging is done completely anonymously.)
Why has it taken so long to post the winning source?
This is somewhat my (Simon Cooper's) fault. I do apologize to the IOCCC community for this! Judging does take quite a lot of time, and I over-committed myself several times this year. Without divulging too much, we do look at and work out what every entry does.
Final Comments
Please send us comments and suggestions what we have expressed above. Also include anything else that you would like to see in future contests. Send such email to:
questions@ioccc.org
IMPORTANT NOTE: The email addresses found above are for historical purposes only, and should not be used today. 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.