NOTE: This code is currently under alpha-test.

Form an IOCCC entry as an XZ compressed tarball file.

For examples and more information, try:

    man ./mkiocccentry.1

The official IOCCC entry Rule 2b size tool.

This code is based on code by @SirWumpus (Anthony Howe):

See @SirWumpus's iocccsize repo

For more information and examples, try:

    man ./iocccsize.1

The official IOCCC tarball validation checker.

It is invoked by mkiocccentry; txzchk in turn uses fnamchk to make sure that the tarball was correctly named and formed (i.e. the mkiocccentry tool was used).

This tool was written in 2022 by @xexyl (Cody Boone Ferguson). See https://xexyl.net and https://ioccc.xexyl.net.

For more information and examples, try:

    man ./txzchk.1

The official IOCCC XZ compressed tarball filename sanity checker tool.

For more information and examples, try:

    man ./fnamechk.1

The official IOCCC .info.json sanity checker tool. Invoked by mkiocccentry after the .info.json file has been created, it will attempt to validate the file. If it does not successfully validate the file there is a mismatch between what is expected and what is actually there and mkiocccentry will fail.

As a stand-alone tool it will report whether the file is a validly formed .info.json file. See also jauthchk.

NOTE: This tool and jauthchk are very much works in progress and as of 10 March 2022 it was decided that the parsing should be done via flex(1) and bison(1) which is being worked on in jparse (see below).

In time the two tools (jinfochk and jauthchk) will be merged into one tool which can parse one or both of .info.json and .author.json. This is because some fields MUST be the same value in both files.

For more information and examples, try:

    man ./jinfochk.1

The official IOCCC .author.json sanity checker tool. Invoked by mkiocccentry after the .author.json file has been created, it will attempt to validate the file. If it does not successfully validate the file there is a mismatch between what is expected and what is actually there and mkiocccentry will fail.

As a stand-alone tool it will report whether the file is a validly formed .author.json file. See also jinfochk.

NOTE: This tool and jinfochk are very much works in progress and as of 10 March 2022 it was decided that the parsing should be done via flex(1) and bison(1) which is being worked on in jparse (see below).

In time the two tools (jauthchk and jinfochk) will be merged into one tool which can parse one or both of .author.json and .author.json. This is because some fields MUST be the same value in both files.

For more information and examples, try:

    man ./jauthchk.1

The official IOCCC JSON parser written in C via flex(1) and bison(1).

It takes a block of memory from either a file (stdin or a text file) or a string (via -s option) and parses it as JSON, reporting if it is validly formed JSON or not.

As of 26 May 2022 it does not yet create a parse tree for other tools like the jinfochk and jauthchk tools. Some things still have to be worked out. Once this is done the other two tools can be finished.

NOTE: At the risk of stating the obvious this tool is very much a work in progress. Good progress is being made but more thought and time is still required.

For more information and examples, try:

    man ./jparse.1