Landon Curt Noll
81b4f460b7
The `display_as` field in an `.entry_json` file must match the regex `^[a-z][0-9a-z]*$` now. This is needed to reduce errors during the final round while converting a potential submission to entry form. Modify `1992/buzzard.2/.entry.json` and `1993/rince/.entry.json` to change `display_as` field to use lower case. Correct `2012/omoikane/.entry.json` to correctly reflect changes made by commit2955e5d07eand commit2955e5d07e. Change `bin/cvt-submission.sh` to verify that the `display_as` matches the above regex. Changed `bin/cvt-submission.sh` VERSION from "2.2.2 2025-06-30" to "2.3.0 2025-07-02". Rebuild all tarballs, both at the entry and the year level due recent changes to `var.mk`, `1337.mk`, and `ioccc.css`. Rebuild sitemap due to the changes above. Ran `make update` to test and 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.