Cody Boone Ferguson
c3b44449cc
The script set the URL for the tarball of all entries in the year to: $YYYY/$YYYY.tar.bz2 but the link is relative so for 1984, for example, it would link to 1984/1984/1984.tar.bz2 which obviously is a 404. I also changed the formatting and wording of the link. It now is all bold and it says instead (for example with 1984): 'Download all winning entries from 1984'. Before it still referred to 'entry source' but it is all entries and more than just the source. This commit does not mean that the YYYY/index.html files have been checked (though it's likely that all should be okay at this point) but the manifest of entries and the tarball of all entries of the year should at least be good.
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.