Cody Boone Ferguson
0d65af1b2b
The entries 2004/hibachi and 2005/mynx have unobfuscated code now. 2004/hibachi has a configure script that is used along the lines of the original entry (with some adjustments and fixes) and the hibachi.alt.c had to have ctype.h included too. The directory src/localhost was copied to src-alt/localhost but the rest of src/ was from Anthony. The Makefile had to be updated to build this version. 2005/mynx does have a configure script but it is, just like the original entry, unused and so the unobfuscated (in source-alt/) is also unused. The mynx.alt.c was changed to mynx.alt2.c and the unobfuscated code was made mynx.alt.c. Updated manifest, rebuilt .entry.json and index.html files. After a question is answered and taken care of (in one of 199[1-3]/ant - not sure which one) issue #2513 can possibly be closed as complete (though the manifest updates will have to be looked at more when 2004 and 2005 are reviewed).
Seventeenth 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.
The IOCCC has a website and now has a number of international mirrors. The primary website can be found at https://www.ioccc.org/.
Remarks on some of the entries
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, utilities, programs that output images and a one-liner that is incredibly compact for what it can do.
The Best abuse of the guidelines is technically allowed by the rules. This year we allowed it due to the functionality of the program. This entry is one of the easiest to read! Don't assume you can win using similar techniques next time ... :-)
This year a single person won two awards! We also had repeat authors with their 6th, 4th and 2nd winning entries this year! (Please note that judging is done completely anonymously. Be warned that we may disqualify entries that reveal the identity of the submitter.)
Remarks on some 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 re-submit 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.