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.
To build:
make all
To use:
make all
NOTE: that's not a typo or mistake but one can also do:
./o
Judges' remarks:
We changed the alias that the author's suggested alias from a C-shell alias to a Bourne-like shell alias.
Note that shst.c is renamed to stig.c in the distribution.
WARNING: This program's how to compile is too specific to a particular shell.
The obfuscation of this program is more related to shell obfuscation than C
obfuscation. This type of entry will not be permitted in future contests.
Author's remarks:
If you like shell programming you may also admire my creative quoting. (I use
echo to create an alias which when run calls cc with the -D option to create
a C macro with double quotes in it. ARRRRRGGGHHH!)
The program is totally portable, but the compile commands are very shell specific so don't be TOO mad at me if they don't work for you.
If you want to put these commands in a Makefile you must add 4 - four - backslashes at the end on first line. (At least that's what works here.)
If everything works correctly it create an executable named o which checks
whether your compiler supports nested comments. I've stolen the "/*/*/0*/**/1"
from somewhere so don't give me any points for it. Of course neither ANSI nor
K&R support nested comments when properly implemented, but what the heck.