Cody Boone Ferguson
c50835517f
In the case of two which had an abstract (.entry.json file) that includes one (in one case) '<' or two (in another case) '<'s a markdown code block had to be used as otherwise the abstract would have to have a < which looks even worse. This is not ideal but if we want it to pass lint this is what has to be done. Use of json \uxxxx won't work as that encodes it to < literally. In the case of 2018/burton[12] the author had a section called Coda. This conflicted with the problem that all generated html files have such a section. To fix this problem I renamed it 'Final remarks'. Not ideal but at least it now passes as valid. There were a number of different kinds of problems and in one case the symbols < and > could be fixed by changing it to a code block (which it should have been anyway) - that was 2020/ferguson1 I think.
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.