Landon Curt Noll
f29b37e49a
Prepare for the winners of **IOCCC28**. > However these are not the 2024 droids you are looking for. :-) The HTML menu (both JavaScript and non-JavaScript) has been updated. The `Status -> Rules and guidelines' have been replaced with two separate menus `Status -> IOCCC rules` and `Status -> IOCCC guidelines`. Added a new top level `social.html` page: built from a new `social.md`. Sorted rules for building specific web pages in the top level `Makefile`. Added `make social` to make the `social.html` page from `social.md`. The `bin/gen-top-html.sh` now is able to process a argument of **social** to process the new top level `social.html` page. Changed `bin/gen-top-html.sh` VERSION from "2.0.0 2025-03-13" to "2.0.1 2025-07-25". Below `About -> Home page` a new `About -> IOCCC social media` menu item as added. Because the menu change touched every HTML file, we changed the general copyright date range for HTML files from "1984-2024" to "1984-2025" due to the extensive changes made for **IOCCC28**. Those markdown files that were modified in 2025 had their copyright date range also changed from "1984-2024" to "1984-2025". Rebuilt tarballs and sitemap due to the extensive HTML rebuilding. Ran `make update` to perform the above.
113 lines
3.8 KiB
Markdown
113 lines
3.8 KiB
Markdown
# Twenty Second International Obfuscated C Code Contest
|
|
|
|
|
|
## Standard IOCCC stuff
|
|
|
|
View the `index.html` web page for the given winning entry for information on how
|
|
compile the entry 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.
|
|
|
|
Some ANSI C compilers are not quite as good as they should be. If
|
|
yours is lacking, you may need to compile using gcc instead of your
|
|
local compiler.
|
|
|
|
|
|
### Historical note:
|
|
|
|
The IOCCC has a website and now has a number of international mirrors.
|
|
The primary website can be found at [www.ioccc.org](https://www.ioccc.org).
|
|
|
|
|
|
### Historical update:
|
|
|
|
The IOCCC website once had a number of
|
|
[international mirrors](https://web.archive.org/web/20201030210517/https://www.ioccc.org/mirror.html).
|
|
As of 2020 Dec 29, [GitHub](https://www.github.com) serves as the distributed server farm for the
|
|
[IOCCC winner repo](https://github.com/ioccc-src/winner) that GitHub renders as
|
|
[Official IOCCC website - www.ioccc.org](https://www.ioccc.org).
|
|
|
|
|
|
## Remarks on some of the entries
|
|
|
|
We believe you will again be impressed with this year's winning entries.
|
|
|
|
This year, 9 won 15 awards. For the first time in the history of the contest,
|
|
one person, [Yusuke Endoh](../authors.html#Yusuke_Endoh) won
|
|
4 times while [Adrian Cable](../authors.html#Adrian_Cable)
|
|
won 3 times! It is also worth noting that [Chris
|
|
Mills](../authors.html#Christopher_Mills)' last win was in
|
|
[1993](../years.html#1993).
|
|
Welcome back Chris!
|
|
|
|
We, the judges, were very surprised by this as many of the multiple
|
|
authors submitted very different styles of entries.
|
|
|
|
This year was the first time the [IOCCC size tool](%%REPO_URL%%/2013/iocccsize.c) was used. Entries
|
|
had to print a value 2053 or less when the `-i` flag was used.
|
|
|
|
Several people discovered an undocumented feature in that
|
|
certain comments such as:
|
|
|
|
``` <!---c-->
|
|
///*
|
|
```
|
|
|
|
or:
|
|
|
|
``` <!---c-->
|
|
*\
|
|
/
|
|
```
|
|
|
|
were not correctly parsed by the tool. The guidelines stated:
|
|
|
|
|
|
> In cases where the above summary and the algorithm implemented by the IOCCC
|
|
size tool source code conflict, the algorithm implemented by the IOCCC size tool
|
|
source code is preferred by the judges.
|
|
|
|
... so this abuse was allowed (and encouraged). The judges hope that
|
|
the IOCCC size tool author will patch the tool to block this kind
|
|
of size abuse in future contests.
|
|
|
|
There were some outstanding entries that did not win. Unfortunately
|
|
some very good entries lost because they:
|
|
|
|
* were way way oversized and didn't even attempt to justify their
|
|
excess by a clever abuse of the rules
|
|
* depended on a single obfuscation trick
|
|
* could only be run on a particular vendor's platform
|
|
* were very similar to previous winning entry
|
|
* didn't work as documented
|
|
|
|
We hope that the authors of some of those entries will fix and resubmit them
|
|
for the next IOCCC.
|
|
|
|
There is a risk in submitting an entry that is similar to a well used theme by
|
|
previous winning entries. Previous entries set a very high bar. A new entry must not
|
|
only compete against other submissions from the current year but they must also
|
|
excel over similar previous winning entry in some particularly impressive way.
|
|
|
|
|
|
## Final Comments
|
|
|
|
**IMPORTANT NOTE**: See [contact.html](../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](../faq.html) for additional information on the IOCCC.
|
|
|
|
|
|
<!--
|
|
|
|
Copyright © 1984-2025 by Landon Curt Noll. All Rights Reserved.
|
|
|
|
You are free to share and adapt this file under the terms of this license:
|
|
|
|
Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
|
|
|
|
For more information, see:
|
|
|
|
https://creativecommons.org/licenses/by-sa/4.0/
|
|
|
|
-->
|