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:
./cdupont
Judges' remarks:
Why is the following label necessary?
sorryfor_this_unused_but_very_needed_label:
Notice that if you C beautify (cb) or pre-process this program, it will no longer work correctly, if at all. Go ahead, try it... :-)
NOTE: One should remove the final trailing newline to obtain the original source file. This step is not needed to compile this entry.
Author's remarks:
The source code holds the letters of the message. Each letter, combined with another key letter, is used to compute the coordinates of the next letter and key. Thus, the message is code. That is why I use silly comments, most often badly spaced.
The space character sequence between the words is given by a simple computation in an octal constant (given here as an hex value, of course).
This way, any message can be mixed into a code, since the keys allow you to place the meaningful letters wherever you want.