Files
ioccc/2015/endoh2
Landon Curt Noll f29b37e49a improve HTML menus, add social.html, prep for IOCCC28 winners
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.
2025-07-26 13:06:29 -07:00
..
…
…
…

To build:

    make

To use:

    ./prog

Try:

    ./try.sh

Judges' remarks:

At this point you might be wondering, WTF?*

  • What The Freak (polite form)

  • What's This For? (you may be wondering)

  • What the Fish (python form)

How is this code obfuscated? Well look again:

    less prog.c

    more prog.c

Where did those underscores come from? Well RTFS!**

** Read the Freaking Source (polite form) ** Read The Freaking Screen (polite form)

If you are still puzzled, look at prog.c with your favorite text editor.

Author's remarks:

Follow these instructions literally!

    cat prog.c
    gcc -w -o prog prog.c
    ./prog

You will do a double take.

Hint 1: Do less prog.c. You will see an emphasized string if your terminal supports bold.

Hint 2: Do wc -c prog.c. This is very long one-liner.

Hint 3: Open the source with an editor like vim or emacs.