Cody Boone Ferguson
f0de51a345
Although there were a few lines that I kind of looked over quickly, not evaluating the files in question, those seemed in good state anyway. Often that was binary files. In some cases for example input more information was given but not in all as it was not always clear what it should be and it was not always clear that it was necessary. Some typos were fixed as well. Rebuilt .entry.json and index.html files. A few other files were also modified with some minor fixes like 2006/toledo2/README.md for one example. In that case I believe some binary files were referenced as %%REPO_URL%% but that is incorrect. These files were edited before the index.html files were rebuilt so they should be fine. It should be noted that although I have gone through the entire manifest and it might be that issue #1933 can be closed there is still a chance that when I go through the web pages that I might come across a problem that I will fix at that time. This might or might not be needed but that will be determined later. Now might be a good time to run make www but I will worry about that later (it might or might not even do anything, depending on what was missed).
Twenty Sixth International Obfuscated C Code Contest
Standard IOCCC stuff
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 primary site can be found at www.ioccc.org.
Use make to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.
Read over the Makefile and index.html files for compile/build issues. Your
system may require certain changes (add or remove a library, add or remove a
#define).
Some C compilers are not quite as good as they should be. If yours is lacking, you may need to compile using clang or gcc instead of your local compiler.
Remarks on some of the winning entries
This year's winning entries are impressive!
The Most in need of debugging - 2019/endoh is very inventive in a way it produces its own text!
The Most likely to be awarded - 2019/ciura has an amazing vocabulary!
There are again nods to entries of the years:
These nods to not run afoul of the guideline:
We tend to dislike programs that:
...
are rather similar to previous entries
because the entry 2019/dogon appropriately pays homage to past entries without blatantly reusing their code.
...We'll stop spouting spoilers now. Have fun exploring all the entries!
Remarks on some of submissions that did not win
Some entries tried to get around the size limit by submitting a data file that was really C code and then blindly including code in prog.c.
Quite a few entries suffered from undefined behavior like accessing uninitialized locals and/or reading-writing below the stack. We advise running your entry through valgrind to make sure those mistakes are avoided.
Using extra arguments to main, or arguments of wrong types as a quick and dirty
way of declaring variables is now passé. Clang, for example, rejects them outright.
We hope the authors of some of those entries will fix and re-submit them for the next IOCCC.
Some entries seemed to have a good idea, but the implementation of the idea was limited in scope.
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.