Landon Curt Noll
4ee4c731f7
While not strictly necessary, replacing the two ASCII tab characters in the markdown copyright comment makes it easier to detect problematic TAB indentation within markdown files. After this commit, only 90 markdown files have leading ASCII TAB characters. And again, while not strictly necessary, we can consider running expand on those 90 markdown files to see what effect that might have on the HTML files they produce. Replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters (the default action of the `expand(1)` tool) might have an negative effect on some HTML formatting where **hack-a-round** formatting was attempted to fix broken indentation caused by problematic ASCII TAB characters. Think of this as a baseline for evaluating leading TAB characters within markdown files. TODO: Consider either using `expand(1)` to replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters AND/OR modifying the appropriate `bin` tool to convert leading ASCII TAB characters into multiples of 8 ASCII SPACE characters.
1.8 KiB
Seventh International Obfuscated C Code Contest
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.
This year, the Grand Prize won a standing ovation at USENIX.
The Strangest abuse of the rules award was given this year to stress the fact that starting in 1991, entries should be shell-specific.
This year was the first year that we accepted ANSI C entries. It was interesting to note that the ANSI C entries were as a whole less portable than the K&R C entries. We hope that in future contests people will enter more obfuscated and challenging ANSI C programs.
We would like to thank Barbara Frezza (loving wife of Larry Bassel) for her role as official chef of the contest. Her opinions regarding some of the contest entries were appreciated.
Rules and results were posted to comp.lang.c, comp.sources.unix, and alt.sources. They have been made available on a wide number of USENET archive sites such as uunet.
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.