Files
ioccc/1990/scjones
Landon Curt Noll 81b4f460b7 require display_as to be a lower case word in .entry.json
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 commit 2955e5d07e
and commit 2955e5d07e.

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.
2025-07-02 16:04:33 -07:00
..
2025-01-09 23:11:43 -08:00
2022-09-18 23:37:49 -07:00
2023-07-06 21:49:38 -07:00

To build:

    make all

To use:

    ./scjones

Try:

    ./try.sh

Judges' remarks:

The addition of trigraphs has made it easier to make programs hard to read. It was a dark and stormy night for C when the ANSI C committee added trigraphs to the standard. Too bad that they didn't just simply require a more reasonable ISO character set.

The Author sent us this note after he was informed that he won:

Although I am quite grateful for the "ANSI Committee's Worst Abuse of C" title (were you aware that I am a member of the committee or is the double meaning unintentional?), I was really hoping for something more along the lines of "Closest Resemblance to Line Noise." :-)

... it was unintentional.

Author's remarks:

Since this year's contest is dedicated to ANSI C, here is a strictly conforming entry. In accordance with the ANSI definition of a strictly conforming program it does not produce output dependent on any unspecified, undefined, or implementation defined behavior, and it does not exceed any of the minimum implementation limits. It adheres to all of the syntactic and semantic constraints of the standard: it #includes the relevant headers for the functions it uses, and it uses the EXIT_SUCCESS and EXIT_FAILURE macros to return a correct success/fail status to the invoking program. It also uses trigraphs for characters which are not in the Invariant Code Set of ISO 646:1983, so it will be portable to machines with deficient (from C's standpoint) character sets. In short, it should be very widely portable. As an extra added attraction, all of the lines are under 72 characters long, which would allow for sequence numbers to be punched in columns 73-80 :-).