Cody Boone Ferguson
f4c21b9094
Where there is not a direct post when referring to a USENET group (for results etc.) it is no longer a link to the group itself but just made italic. That means only 1984 has it and only for the contest announcement. In 1989 the point about the Makefiles for fubar and tromp have been clarified a bit. They were ambiguous before: it could have been read as the Makefile for ALL entries but it was only for that entry. Also since these points are about the Makefile (and in particular portability of the original or alt versions) I moved the paragraph to right under the part about running make to compile (this part has some additional fixes that will be applied later on). The years: 1984, 1985, 1986, 1987 and 1989 were updated. There was nothing to do (for this commit) for 1988 but there is a change that will be made after discussion.
2.0 KiB
Fourth International Obfuscated C Code Contest
View the index.html web page for the given winning entry for information on how
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 1997 suggested even more categories than in 1986.
Hints for what to do and not to do were also given in the rules.
For example, a simple excessive abuse of /lib/cpp was discouraged unless the
abuse was unusual. The mailboxes for the contest were moved from nsc to amdahl.
The practice of posting a preliminary set of rules for the next year was started
this year.
Rules and results were posted to comp.lang.c and comp.unix.wizards with an announcement in news.announce.important. Micro/Systems Journal published the 1987 winning entries. Mary Ann Horton included a version of the 1987 winning entries in an appendix of her C book Portable C Software International Edition (published under the name Mark R Horton). The first announcement of winning entries at the Summer 87 USENIX was helped by a small fly that danced all over the foils.
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.