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
Fifth 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.
The maximum size of entries was raised from 1024 to 1536 bytes, however smaller entries were encouraged. Due to the Best abuse of the rules entry of 1987, a limit of 160 chars in the compile line was introduced.
This year, the Best of Show was given to the most unusual
entry and the best abuse of the C Preprocessor rather than the most well rounded
entry.
Rules and results were posted to comp.lang.c, comp.sources.unix and alt.sources. The 1988 winning entries will be published in the Micro/Systems Journal.
Winning entries for previous years were repackaged with each year being in its own directory. Makefiles and hints were also provided. The package was posted to the comp.sources.unix newsgroup. They are also available on a wide number of USENET archive sites.
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.