From 0bc6c3e4134d13fb9644b1493fce9762bff260eb Mon Sep 17 00:00:00 2001 From: Landon Curt Noll Date: Wed, 17 Jul 2024 03:11:19 -0700 Subject: [PATCH] improve markdown references to FAQ entries We quasi-canonicalized markdown links to FAQ entries. **IMPORTANT NOTE**: This is a useful step in completing issue #2417. This commit is consistent with the top level TODO comment requirements. Nevertheless, this changes made by this commit needs to be examined and in some cases improved. A link to an FAQ entry is of the form: ``` FAQ on "[the link text](....faq.html#string)" FAQ on "[the link text](....faq.html#string)" ``` The "FAQ" is at the start of the line, or in rare cases is preceded only by whitespace. The reference to the FAQ starts outside of the markdown link with the string **FAQ ON "**. After the markdown link is a **"** followed by either the end of line or a single punctuation character such as a period or comma. We reduced the size of "the link text" that refer to an FAQ to at most 3 words. In some cases the sentence and/or text surrounding the markdown link to a FAQ may need to be further adjusted to better accommodate this new style. **IMPORTANT NOTE**: References to a FAQ entry are on a separate line. p.s. When linking to the `faq.html` file itself, we use markdown of the form "`the [IOCCC FAQ](..../faq.html)`" and place the word "the" outside of the "IOCCC FAQ" link text. Given the above system (and because references to an FAQ entry is on a separate line), the following command shows links to FAQ entries, sorted by FAQ entry "link #name" so that one may evaluate the way a given FAQ entry is referenced: ```sh find * -name '*.md' -print0 | xargs0 grep -E '^[[:space:]]*FAQ on "' | sed -e 's/^\([^:]*\):\( *FAQ on "[^#]*\)#\([^)]*\)\()".*\)$/#\3\t\1\t\2#\3\4/' | sort ``` The above command shows the value of consistency when it comes to FAQ references. **NOTE**: There are a few differences on how a given FAQ is references. That is probably OK as there is NOT an "total mandate" that all references to a given FAQ must have the same "link text" for example. On the other hand if references to a given FAQ can be identical, that might be helpful. We are certain that in some contexts the "link text" might need to change. Should we decide to change the way FAQ are referenced, we will be able to modify identify and modify them with greater ease.' Examine the changes made by this commit and adjust and/or improve as needed. Performed `make www` to accomplish the above and to test under macOS. --- 1984/README.md | 2 +- 1984/index.html | 2 +- 1985/README.md | 2 +- 1985/index.html | 2 +- 1986/README.md | 2 +- 1986/index.html | 2 +- 1987/README.md | 2 +- 1987/index.html | 2 +- 1988/README.md | 2 +- 1988/index.html | 2 +- 1989/README.md | 2 +- 1989/index.html | 2 +- 1990/README.md | 2 +- 1990/index.html | 2 +- 1991/README.md | 2 +- 1991/index.html | 2 +- 1992/README.md | 2 +- 1992/index.html | 2 +- 1993/README.md | 2 +- 1993/cmills/README.md | 4 +- 1993/cmills/index.html | 4 +- 1993/index.html | 2 +- 1993/jonth/README.md | 5 +- 1993/jonth/index.html | 5 +- 1994/README.md | 2 +- 1994/index.html | 2 +- 1995/README.md | 2 +- 1995/index.html | 2 +- 1996/README.md | 2 +- 1996/index.html | 2 +- 1998/README.md | 2 +- 1998/index.html | 2 +- 2000/README.md | 2 +- 2000/index.html | 2 +- 2000/thadgavin/README.md | 8 +- 2000/thadgavin/index.html | 8 +- 2001/README.md | 2 +- 2001/index.html | 2 +- 2001/ollinger/README.md | 2 +- 2001/ollinger/index.html | 2 +- 2004/README.md | 2 +- 2004/index.html | 2 +- 2005/README.md | 2 +- 2005/boutines/README.md | 4 +- 2005/boutines/index.html | 4 +- 2005/index.html | 2 +- 2005/jetro/README.md | 5 +- 2005/jetro/index.html | 5 +- 2006/README.md | 2 +- 2006/index.html | 2 +- 2011/README.md | 2 +- 2011/index.html | 2 +- 2012/README.md | 2 +- 2012/index.html | 2 +- 2012/zeitak/README.md | 4 +- 2012/zeitak/index.html | 4 +- 2013/README.md | 2 +- 2013/endoh3/README.md | 5 +- 2013/endoh3/index.html | 5 +- 2013/index.html | 2 +- 2014/maffiodo1/README.md | 5 +- 2014/maffiodo1/index.html | 5 +- 2015/endoh1/README.md | 4 +- 2015/endoh1/index.html | 4 +- 2018/README.md | 2 +- 2018/algmyr/README.md | 4 +- 2018/algmyr/index.html | 4 +- 2018/bellard/README.md | 8 +- 2018/bellard/index.html | 8 +- 2018/burton1/README.md | 4 +- 2018/burton1/index.html | 4 +- 2018/giles/README.md | 5 +- 2018/giles/index.html | 5 +- 2018/index.html | 2 +- 2018/poikola/README.md | 5 +- 2018/poikola/index.html | 5 +- 2019/README.md | 2 +- 2019/giles/README.md | 4 +- 2019/giles/index.html | 4 +- 2019/index.html | 2 +- 2019/mills/README.md | 5 +- 2019/mills/index.html | 4 +- 2020/README.md | 2 +- 2020/giles/README.md | 5 +- 2020/giles/index.html | 5 +- 2020/index.html | 2 +- contact.html | 34 ++- contact.md | 34 ++- faq.html | 422 +++++++++++++++++++++++++------------- faq.md | 418 ++++++++++++++++++++++++------------- index.html | 7 +- index.md | 7 +- markdown.html | 7 +- markdown.md | 5 +- news.html | 9 +- news.md | 9 +- next/guidelines.html | 39 ++-- next/guidelines.md | 39 ++-- next/rules.html | 45 ++-- next/rules.md | 45 ++-- status.html | 11 +- status.md | 13 +- thanks-for-help.html | 162 +++++++-------- thanks-for-help.md | 161 ++++++++------- 104 files changed, 1051 insertions(+), 687 deletions(-) diff --git a/1984/README.md b/1984/README.md index 1f2f2beb9..a5873fb84 100644 --- a/1984/README.md +++ b/1984/README.md @@ -19,7 +19,7 @@ post](https://groups.google.com/g/net.lang.c/c/lx-TAuEyeRI/m/HdOOnNx6LC0J). **IMPORTANT NOTE**: See [contact.html](../contact.html) for up to date contact details as well as details on how to provide fixes to any of the entries. -See also [the IOCCC FAQ](../faq.html) for additional information on the IOCCC. +See also the [IOCCC FAQ](../faq.html) for additional information on the IOCCC. diff --git a/1993/jonth/index.html b/1993/jonth/index.html index 35c4b4a4c..fb68e74f1 100644 --- a/1993/jonth/index.html +++ b/1993/jonth/index.html @@ -409,8 +409,9 @@ Location: NO - Kingdom of Norway (

To build:

NOTE: this entry requires the X11/Xlib.h header file and the X11 library to -compile. See the FAQ on how to run entries that require X11 if -you need help.

+compile. See the +FAQ on “X11” +if you need help.

    make all

To use:

    ./jonth     # must be run on an X11 server
diff --git a/1994/README.md b/1994/README.md index 8ce53d94b..7e294db28 100644 --- a/1994/README.md +++ b/1994/README.md @@ -117,7 +117,7 @@ as well as details on how to provide fixes to any of the entries. purposes only, and should not be used today. See [contact.html](../contact.html) for up to date contact details as well as details on how to provide fixes to any of the entries. -See also [the IOCCC FAQ](../faq.html) for additional information on the IOCCC. +See also the [IOCCC FAQ](../faq.html) for additional information on the IOCCC. ## Credits diff --git a/1994/index.html b/1994/index.html index 5b4b3e958..2df4a9f10 100644 --- a/1994/index.html +++ b/1994/index.html @@ -482,7 +482,7 @@ as well as details on how to provide fixes to any of the entries.

purposes only, and should not be used today. See contact.html for up to date contact details as well as details on how to provide fixes to any of the entries. -See also the IOCCC FAQ for additional information on the IOCCC.

+See also the IOCCC FAQ for additional information on the IOCCC.

Credits

We would like to thank Barbara Frezza for her role as official chef of the contest. Landon Curt Noll and Larry Bassel appreciated the opportunity diff --git a/1995/README.md b/1995/README.md index ce91cf2c1..729b69a46 100644 --- a/1995/README.md +++ b/1995/README.md @@ -65,7 +65,7 @@ us a line. We enjoy seeing who, where and how the contest is used. purposes only, and should not be used today. See [contact.html](../contact.html) for up to date contact details as well as details on how to provide fixes to any of the entries. -See also [the IOCCC FAQ](../faq.html) for additional information on the IOCCC. +See also the [IOCCC FAQ](../faq.html) for additional information on the IOCCC. ## Credits diff --git a/1995/index.html b/1995/index.html index 91c49b0b7..60e7e521d 100644 --- a/1995/index.html +++ b/1995/index.html @@ -444,7 +444,7 @@ us a line. We enjoy seeing who, where and how the contest is used.

purposes only, and should not be used today. See contact.html for up to date contact details as well as details on how to provide fixes to any of the entries. -See also the IOCCC FAQ for additional information on the IOCCC.

+See also the IOCCC FAQ for additional information on the IOCCC.

Credits

We would like to thank Barbara Frezza for her role as official chef of the contest. Landon Noll, Larry Bassel and Sriram Srinivasan diff --git a/1996/README.md b/1996/README.md index 30d461325..3f5ac59f8 100644 --- a/1996/README.md +++ b/1996/README.md @@ -85,7 +85,7 @@ us a line. We enjoy seeing who, where and how the contest is used. purposes only, and should not be used today. See [contact.html](../contact.html) for up to date contact details as well as details on how to provide fixes to any of the entries. -See also [the IOCCC FAQ](../faq.html) for additional information on the IOCCC. +See also the [IOCCC FAQ](../faq.html) for additional information on the IOCCC.

To build:

-

This entry requires SDL. See 3.8 - How do I compile an IOCCC entry that -requires SDL1 or SDL2? for information on how to install it if you +

This entry requires SDL. See +FAQ on “SDL1 and SDL2” +for information on how to install it if you haven’t already.

If you have SDL installed:

    make
diff --git a/2006/README.md b/2006/README.md index 678e172e0..40de57cfd 100644 --- a/2006/README.md +++ b/2006/README.md @@ -49,7 +49,7 @@ of the submitter). **IMPORTANT NOTE**: See [contact.html](../contact.html) for up to date contact details as well as details on how to provide fixes to any of the entries. -See also [the IOCCC FAQ](../faq.html) for additional information on the IOCCC. +See also the [IOCCC FAQ](../faq.html) for additional information on the IOCCC. make diff --git a/2014/maffiodo1/index.html b/2014/maffiodo1/index.html index 67efc4ee2..25ce77d2e 100644 --- a/2014/maffiodo1/index.html +++ b/2014/maffiodo1/index.html @@ -408,8 +408,9 @@ Location: IT - Italian Republic (<

To build:

-

This entry requires SDL to be installed. See FAQ 3.8 if you -don’t know how to do this for your system.

+

This entry requires SDL to be installed. See +FAQ on “SDL1 and SDL2” +if you don’t know how to do this for your system.

    make

Bugs and (Mis)features:

The current status of this entry is:

diff --git a/2015/endoh1/README.md b/2015/endoh1/README.md index 1f056987f..5f95d5e6f 100644 --- a/2015/endoh1/README.md +++ b/2015/endoh1/README.md @@ -5,8 +5,8 @@ ``` NOTE: this program requires the tool `tcpserver` to use. If you do not have this -program see [FAQ 3.14 - How do I compile and install tcpserver for entries that -require it](../../faq.html#tcpserver). +program see +FAQ on "[tcpserver](../../faq.html#tcpserver)". ## To use: diff --git a/2015/endoh1/index.html b/2015/endoh1/index.html index 850eb0225..f6ce38f68 100644 --- a/2015/endoh1/index.html +++ b/2015/endoh1/index.html @@ -415,8 +415,8 @@ Location: JP - Japan

To build:

    make

NOTE: this program requires the tool tcpserver to use. If you do not have this -program see FAQ 3.14 - How do I compile and install tcpserver for entries that -require it.

+program see +FAQ on “tcpserver”.

To use:

    tcpserver -v 127.0.0.1 10333 ./prog ioccc.txt

Then connect to http://localhost:10333 with your browser.

diff --git a/2018/README.md b/2018/README.md index 407c790bd..4fff8d22f 100644 --- a/2018/README.md +++ b/2018/README.md @@ -90,7 +90,7 @@ the idea was limited in scope. **IMPORTANT NOTE**: See [contact.html](../contact.html) for up to date contact details as well as details on how to provide fixes to any of the entries. -See also [the IOCCC FAQ](../faq.html) for additional information on the IOCCC. +See also the [IOCCC FAQ](../faq.html) for additional information on the IOCCC. diff --git a/2018/giles/index.html b/2018/giles/index.html index c1d2c4947..b418d8b31 100644 --- a/2018/giles/index.html +++ b/2018/giles/index.html @@ -408,8 +408,9 @@ Location: AU - Commonwealth of Australi

To build:

-

This entry requires SDL2 to be installed. See FAQ 3.8: How do I compile an -IOCCC entry that requires SDL1 or SDL2? if you don’t have it +

This entry requires SDL2 to be installed. See +FAQ on “SDL1 and SDL2” +if you don’t have it installed and don’t know how to do so.

    make

To use:

diff --git a/2018/index.html b/2018/index.html index a64bc1010..b05e1d060 100644 --- a/2018/index.html +++ b/2018/index.html @@ -460,7 +460,7 @@ the idea was limited in scope.

Final Comments

IMPORTANT NOTE: See contact.html for up to date contact details as well as details on how to provide fixes to any of the entries. -See also the IOCCC FAQ for additional information on the IOCCC.

+See also the IOCCC FAQ for additional information on the IOCCC.

@@ -4004,7 +4120,9 @@ app from time to time to view IOCCC mastodon updates.

by going to your entry in the authors.html web page and viewing the string that follows the author_handle: line.

If you are not someone who has won a previous IOCCC, you will be able to select -a potential author_handle when you form your submission tarball (see FAQ 0.0).

+a potential author_handle when you form your submission tarball (see +FAQ on “how to submit” +).

Helpful Hint: If an author clicks on their author_handle: line link, you will be taken to that author’s author_handle.json file.

For example, Brian Westley can view his @@ -4013,12 +4131,20 @@ Clicking on the author_handle shows the contents of the Brian_Westley.json file.

IMPORTANT NOTE: An author who has won a previous IOCCC is encouraged to reuse their author_handle so that new winning entries can be associated with the same author.

-

See FAQ 5.5 for information about how to update +

See +FAQ on “fixing author information” +for information about how to update and/or correct IOCCC author information.

-

See FAQ 6.5 for more information about author handles.

-

See FAQ 6.6 for information about the contents of these JSON file and +

See +FAQ on “author handle” +for more information about author handles.

+

See +FAQ on “author_handle.json” +for information about the contents of these JSON file and how they are used.

-

See FAQ 6.9 for more information on terms such as author, entry, and submission.

+

See +FAQ on “Author, Entry, Submission” +for more information on terms such as author, entry, and submission.

FAQ 6.14: How do I set certain tabstops for viewing source code in vi(m)?

@@ -4046,8 +4172,8 @@ It should look something like:

width=912 height=160>

Simply move your mouse cursor over the category you want and then click on the item you wish to view that drops down from the category.

-

This is likely how it will appear with a tablet device in landscape -mode, too, unless JavaScript is +

This is likely how it will appear with a tablet device in landscape +mode, too, unless JavaScript is disabled.

Mobile menus

@@ -4082,10 +4208,10 @@ to Menus on tablet devices (e.g. iPads)

With tablets, it likely depends on the orientation you have your device in. If it’s -in portrait mode you likely will see the menu that one will get on a mobile +in portrait mode you likely will see the menu that one will get on a mobile phone.

If, on the other hand, you are using landscape mode, say on an iPad Pro 11 inch -4th generation, then you will likely see the menu as you would on a desktop or +4th generation, then you will likely see the menu as you would on a desktop or laptop.

@@ -4095,7 +4221,7 @@ very possibly have to press and hold the menu icon:

menu open icon

-

to activate it. You can then use it as you would on a mobile +

to activate it. You can then use it as you would on a mobile phone.

Browsing the website on mobile devices with a browser bug
@@ -4107,10 +4233,10 @@ mode in macOS) the menu does not work at all. That is to say one might see:

width=1242 height=531>

Notice how the menu icon is not even there! This happens in both portrait mode and landscape mode.

-

In this case one will have to use the no JavaScript +

In this case one will have to use the no JavaScript menu. If you have a fix for this that does NOT affect the usability of desktops, laptops or other mobile devices, please -consider fixing it and opening a pull request or at +consider fixing it and opening a pull request or at least report it as an issue (choose the category Website issue).

diff --git a/faq.md b/faq.md index d96be3ea4..12acc25c4 100644 --- a/faq.md +++ b/faq.md @@ -203,7 +203,9 @@ where: * remarks.md - Remarks about your entry in markdown format: see [FAQ 2.1](#remarks_md) for more info. + Remarks about your entry in markdown format: see + FAQ on "[remarks.md](#remarks_md)" + for more info. * [file ...] @@ -258,7 +260,8 @@ frequently submitted theme, be sure that it is obfuscated in several new and novel ways. **IMPORTANT HINT**: Be sure to **clearly explain** near the beginning -of your `remarks.md` file, see [FAQ 2.1](#remarks_md), +of your `remarks.md` file, see +FAQ on "[remarks.md](#remarks_md)", **why you are submitting a entry based on a frequently submitted theme** and **how compares with previous IOCCC winners** of the same theme. @@ -358,7 +361,8 @@ state something along the lines of: ``` **FAIR WARNING**: Be sure to **clearly explain** near the beginning -of your `remarks.md` file, see [FAQ 2.1](#remarks_md), +of your `remarks.md` file, see +FAQ on "[remarks.md](#remarks_md)", **why you are submitting a entry based on a frequently submitted theme** and **how compares with previous IOCCC winners** of the same theme. @@ -523,7 +527,8 @@ information, they will ask (either in public or suggest a private conversation). Again, **please** don't hesitate to ask: Your question may be something that others are wondering about as well! -See also [FAQ about making suggestions](#feedback). +See also +FAQ on "[rules, guidelines, tools feedback](#feedback)".
@@ -533,7 +538,7 @@ See also [FAQ about making suggestions](#feedback).
The IOCCC makes extensive use of [markdown](https://daringfireball.net/projects/markdown/). -For example, we [submitting to the IOCCC](faq.html#submit), we have people +For example, we [submitting to the IOCCC](#submit), we have people to submit remarks about entry in markdown format. Every [winning IOCCC entry](years.html) uses a `README.md` markdown file as the basis for forming the `index.html` web page for that entry. @@ -616,8 +621,10 @@ submission: * The **alt URL** of this author, or `null` if not provided. - `mastodon` (null or double quoted string) - * The **[Mastodon](#try_mastodon) handle** of this author in the form of `@user@domain`, or - `null` if not provided. + * The Mastodon handle of this author in the form of `@user@domain`, or + `null` if not provided. See + FAQ on "[Mastodon](#try_mastodon)" + for more information. - `github` (null or double quoted string) * The **[GitHub](https://github.com) account** of this author in the form of `@user`, or `null` if not @@ -650,9 +657,12 @@ submission: **NOTE:** if you have won before, we **ENCOURAGE** you to use the same handle of your previous winning entries, to help in organising the - [authors.html](authors.html) page and the author JSON file (see: [What is an - author handle?](#author_handle_faq) and [What is an `author_handle.json` - file and how are they used?](#author_json)). + [authors.html](authors.html) page and the author JSON file. + See + FAQ on "[author handle](#author_handle_faq)" + and + FAQ on "[author_handle.json](#author_json)" + for more information. - `author_number` (number) * This author number in the `authors` array. @@ -783,7 +793,10 @@ The file also contains the following details: **NOT** email the [Judges](judges.html) your submission! - `formed_timestamp` (number) - * Seconds since epoch when `.auth.json`/[.info json](#info_json) was formed (see `gettimeofday(2)`). + * Seconds since epoch when `.auth.json was formed (see `gettimeofday(2)`). + See also + FAQ on "[.info.json](#info_json)" + for more inforation. **NOTE:** this **MUST** be greater than or equal to `MIN_TIMESTAMP` (see [soup/limit_ioccc.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/limit_ioccc.h) @@ -853,14 +866,23 @@ This file is constructed by the `mkiocccentry(1)` **prior to** forming the xz compressed tarball of your submission. The `.info.json` file contains information about the submission, in JSON format. The JSON `manifest` array contains information about the files of the submission, -**including** the **mandatory** [.auth.json](#auth_json), [.info.json](#info_json), -C source and [remarks](#remarks) files. In particular: +**including** the **mandatory** `.auth.json` file, +the **mandatory** `remarks.md` file, +and the **mandatory** C source file. +See the +FAQ on "[.auth.json](#auth_json)" +and +FAQ on "[remarks.md](#remarks_md)" +for more inforation. - `info_JSON` (double quoted string) * This `MUST` be `".info.json"`, defined as `INFO_JSON_FILENAME` in [soup/entry_util.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h) in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/), and - it is the [.info.json](#info_json) file that `mkiocccentry` forms. + it is the `.info.json` file that `mkiocccentry` forms. + See the + FAQ on "[.info.json](#info_json)" + for more information. **NOTE:** if this is **NOT** the case you stand a great chance of having your submission rejected for violating [Rule 17](next/rules.html#rule17)! @@ -869,7 +891,10 @@ C source and [remarks](#remarks) files. In particular: * This `MUST` be `".auth.json"`, defined as `AUTH_JSON_FILENAME` in [soup/entry_util.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h) in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/), and - it is the [.auth.json](#auth_json) file that `mkiocccentry` forms. + it is the `.auth.json` file that `mkiocccentry` forms. + See the + FAQ on "[.auth.json](#auth_json)" + for more inforation. **NOTE:** if this is **NOT** the case you stand a great chance of having your submission rejected for violating [Rule 17](next/rules.html#rule17)! @@ -891,7 +916,10 @@ C source and [remarks](#remarks) files. In particular: * This `MUST` be `"Makefile"`, defined as `MAKEFILE_FILENAME` in [soup/entry_util.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h) in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/), and - is your [Makefile](#makefile). + is your `Makefile` file. + See the + FAQ on "[Makefile](#makefile)" + for more information. **NOTE:** if this is **NOT** the case you stand a great chance of having your submission rejected for violating [Rule 17](next/rules.html#rule17)! @@ -903,7 +931,10 @@ C source and [remarks](#remarks) files. In particular: * This `MUST` be `"remarks.md"`, defined as `REMARKS_FILENAME` in [soup/entry_util.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/entry_util.h) in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/), and - is your [remarks.md](#remarks). + is your `remarks.md]` file. + See the + FAQ on "[remarks.md](#remarks_md)" + for more information. **NOTE:** if this is **NOT** the case you stand a great chance of having your submission rejected for violating [Rule 17](next/rules.html#rule17)! @@ -1134,31 +1165,50 @@ The file also contains the following details: - `Makefile_override` (boolean) * `true` if the user overrides any warnings about an incomplete/incorrect - [Makefile](#makefile), else `false`. + `Makefile file, else `false`. - **NOTE:** if the [Makefile](#makefile) has no problems and this is `true` then + **NOTE:** if the `Makefile` file has no problems and this is `true` then you stand a good chance of having your submission rejected for violating [Rule 17](next/rules.html#rule17)! + See the + FAQ on "[Makefile](#makefile)" + for more information. + - `first_rule_is_all` (boolean) - * `true` if the first rule in the [Makefile](#makefile) is - `all`, else `false`. + * `true` if the first rule in the `Makefile` file is `all`, else `false`. + + See the + FAQ on "[Makefile](#makefile)" + for more information. - `found_all_rule` (boolean) - * `true` if the [Makefile](#makefile) has an `all` rule, else - `false`. + * `true` if the `Makefile` file has an `all` rule, else `false`. + + See the + FAQ on "[Makefile](#makefile)" + for more information. - `found_clean_rule` (boolean) - * `true` if the [Makefile](#makefile) has a `clean` rule, else - `false`. + * `true` if the `Makefile` file has a `clean` rule, else `false`. + + See the + FAQ on "[Makefile](#makefile)" + for more information. - `found_clobber_rule` (boolean) - * `true` if the [Makefile](#makefile) has a `clobber` rule, - else `false`. + * `true` if the `Makefile` file has a `clobber` rule, else `false`. + + See the + FAQ on "[Makefile](#makefile)" + for more information. - `found_try_rule` (boolean) - * `true` if the [Makefile](#makefile) has a `try` rule, else - `false`. + * `true` if the `Makefile` file has a `try` rule, else `false`. + + See the + FAQ on "[Makefile](#makefile)" + for more information. - `test_mode` (boolean) * `true` if the `test` ID was used to form the tarball, else `false`. @@ -1167,7 +1217,7 @@ The file also contains the following details: contest! Please do **NOT** email the [Judges](judges.html) your submission! - `formed_timestamp` (number) - * Seconds since epoch when [.auth.json](#auth_json)/`.info json` was formed (see `gettimeofday(2)`). + * Seconds since epoch when JSON (`.auth.json` or `.info.json`) file was formed (see `gettimeofday(2)`). **NOTE:** this **MUST** be greater than or equal to `MIN_TIMESTAMP` (see [soup/limit_ioccc.h](https://github.com/ioccc-src/mkiocccentry/blob/master/soup/limit_ioccc.h) @@ -1836,10 +1886,11 @@ Please see the [bugs.html](bugs.html) file for details about known problems with If you have a fix that makes a minimal impact to the entry, then please consider submitting that change in the form of a pull request. -Please see [FAQ 5.2 How may I submit a fix to an IOCCC -entry](#fix_an_entry). See also the [FAQ 6.10 How does someone -make a change to a file and submit that change as a GitHub pull -request](#pull_request) for more information about pull requests. +Please see +FAQ on "[fixing an entry](#fix_an_entry)". +See also the +FAQ on "[GitHub pull request](#pull_request)" +for more information about pull requests. In some cases alternative code has been added that does compile on some or most systems. Check the write up for the entry for "alt" code and possible ways to @@ -1880,10 +1931,10 @@ in question to see if the problem is known, and if a fix is wanted, consider trying to port the code to a 64-bit system and submitting a pull request with that change. Pull requests that fix such code while trying to minimize the impact of any changes and preserving -the spirit of the original code are very welcome! Please see [FAQ -5.2 How may I submit a fix to an IOCCC entry](#fix_an_entry) for -details. See also the [FAQ 6.10 How does someone make a change to -a file and submit that change as a GitHub pull request](#pull_request) +the spirit of the original code are very welcome! Please see +FAQ on "[fixing an entry](#fix_an_entry)" +for details. See also the +FAQ on "[GitHub pull request](#pull_request)" for more information about pull requests. @@ -1902,7 +1953,8 @@ In some cases the [bugs.html](bugs.html) file may note a known macOS problem with an entry. Should you manage to port the entry, and assuming your changes also attempt to preserve the original intent of the IOCCC entry, we would encourage you to submit a pull request with your ported code. -Please see [FAQ 5.2 How may I submit a fix to an IOCCC entry](#fix_an_entry) +Please see +FAQ on "[fixing an entry](#fix_an_entry)" for details. @@ -1927,10 +1979,11 @@ other things that have to be done plus remembering to do it. See if the problem is mentioned in [bugs.html](bugs.html). If you have a change that fixes the problem (even if it just a change to the `Makefile`) that doesn't negatively impact the entry too much, consider submitting that change in the -form of a pull request. Please see [FAQ 5.2 How may I submit a fix to an IOCCC -entry](#fix_an_entry). See also the [FAQ 6.10 How does someone -make a change to a file and submit that change as a GitHub pull -request](#pull_request) for more information about pull requests. +form of a pull request. Please see +FAQ on "[fixing an entry](#fix_an_entry)". +See also the +FAQ on "[GitHub pull request](#pull_request)" +for more information about pull requests.
@@ -2021,10 +2074,15 @@ information. If your system uses **Wayland** and not X11, you might give the IOCCC entries that use X11 a try. They might work but again we do not know. -**IMPORTANT NOTE**: The [IOCCC judges](judges.html) [do not support IOCCC entries](#no_support). +**IMPORTANT NOTE**: The [IOCCC judges](judges.html) **do not support IOCCC entries**. +See the +FAQ on "[no entry support](#no_support)". So if an IOCCC entry that uses X11 fails under **Wayland**, and you wish to provide a fix to the IOCCC entry so that it will run under **Wayland**, -then consider [submitting a fix](#fix_an_entry) so that it will run under **Wayland**. +then consider submitting a fix so that it will run under **Wayland**. +See the +FAQ on "[fixing an entry](#fix_an_entry)" +for more information. Basically: if you discover an entry does not work in Wayland you are welcome to provide **alternate code** that works for Wayland. We will happily credit you in @@ -2033,7 +2091,8 @@ the [thanks-for-help.html](thanks-for-help.html) file. #### Red Hat based Linux -First, see the above note on [installing and starting Xorg](#X11_general). +First, see +FAQ on "[general X11](#X11_general)". Install Xorg and related packages: @@ -2045,13 +2104,16 @@ See also: * [How to Configure X11 in Linux](https://www.wikihow.com/Configure-X11-in-Linux) -**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated). -See the above note for details. +**IMPORTANT NOTE**: The X.org server has been deprecated. +See the +FAQ on "[X.org deprecated](#Xorg_deprecated)" +for more information. #### macOS -First, see the above note on [installing and starting Xorg](#X11_general). +First, see the +FAQ on "[general X11](#X11_general)". However, for macOS, instead of installing the Xorg server, you need to install and launch the [most recent XQuartz](https://www.xquartz.org) application and then run the IOCCC entry from the [Xterm window @@ -2089,13 +2151,16 @@ Note that you can compile the code in your regular terminal prior to opening XQuartz, should you wish to. You can even run it from that terminal and it should open XQuartz. -**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated). -See the above note for details. +**IMPORTANT NOTE**: The X.org server has been deprecated. +See the +FAQ on "[X.org deprecated](#Xorg_deprecated)" +for more information. #### Debian based Linux -First, see the above note on [installing and starting Xorg](#X11_general). +First, see the +FAQ on "[general X11](#X11_general)". According to the [Debian Xorg wiki](https://wiki.debian.org/Xorg), installing X11 requires: @@ -2104,13 +2169,16 @@ X11 requires: sudo apt install xorg ``` -**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated). -See the above note for details. +**IMPORTANT NOTE**: The X.org server has been deprecated. +See the +FAQ on "[X.org deprecated](#Xorg_deprecated)" +for more information. #### Other Linux distributions -First, see the above note on [installing and starting Xorg](#X11_general). +First, see the +FAQ on "[general X11](#X11_general)". For general documentation on installing X11, this [ServerGUI for Ubuntu](https://help.ubuntu.com/community/ServerGUI), and in particular, these @@ -2136,18 +2204,23 @@ For systems that have the `yum(1)` command: sudo yum install --skip-broken --best --exclude xorgxrdp --exclude xorgxrdp-glamor '*xorg*' 'libx*' 'libX*' 'fontconfig*' ``` -**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated). -See the above note for details. +**IMPORTANT NOTE**: The X.org server has been deprecated. +See the +FAQ on "[X.org deprecated](#Xorg_deprecated)" +for more information. #### Package website -First, see the above note on [installing and starting Xorg](#X11_general). +First, see the +FAQ on "[general X11](#X11_general)". See the [X.org](https://x.org/wiki/) foundation website. -**IMPORTANT NOTE**: The [X.org server has been deprecated](#Xorg_deprecated). -See the above note for details. +**IMPORTANT NOTE**: The X.org server has been deprecated. +See the +FAQ on "[X.org deprecated](#Xorg_deprecated)" +for more information.
@@ -2187,7 +2260,9 @@ but this might not be necessary in more modern days especially as we use `sdl-config` and `sdl2-config` which should find the proper paths. +
#### macOS +
If you're using macOS there are at least three ways to obtain it. You can use Homebrew or MacPorts. If you do not wish to use either of those @@ -2268,8 +2343,9 @@ be that you need additional SDL libraries. See the entry's index.html for details. If something is not noted you're welcome to report it as an issue or fix it and make a pull request. -See the [FAQ 6.10 How does someone make a change to a file and submit that change -as a GitHub pull request](#pull_request) for more information about pull requests. +See the +FAQ on "[GitHub pull request](#pull_request)" +for more information about pull requests.
@@ -2582,7 +2658,9 @@ It also possible that you may have discovered a bug in an winning IOCCC entry. If so, you are invited to try and fix the IOCCC entry and submit that fix by way of a [GitHub pull request](https://github.com/ioccc-src/winner/pulls). -Please see [FAQ 5.2](#fix_an_entry) for how to submit a fix to an IOCCC entry. +Please see +FAQ on "[fixing an entry](#fix_an_entry)" +for how to submit a fix to an IOCCC entry.
@@ -2861,9 +2939,9 @@ We recommend trying a method suitable for your environment first, if possible. This depends on your operating system for which we describe a couple below. -In general OpenGL needs X11 to be installed and the X Window Server to be running. -See [FAQ 3.7: How do I run an IOCCC entry that requires X11?](#X11_general) for -general information about X11. +In general OpenGL needs X11 to be installed and the X Window Server to be running. See +FAQ on "[X11](#X11)" +for general information about X11. Once X11 is install and the X Window Server is running, one needs to compile and link with the two libraries, _GL_ and _GLU_: @@ -3014,8 +3092,8 @@ then do: to compile all versions and then run the alternate version (if you have a PDP-11 or VAX-11 you would be able to run the original version). For more help -on compiling entries, see also [3.0 - What Makefile rules are available to -build or clean up IOCCC entries?](#make_rules). +on compiling entries, see also the +FAQ on "[IOCCC Makefile rules](#make_rules)". If you want to view the `index.html` file you can point your browser to the `index.html` file of the winning entry (e.g. `1984/mullender/index.html`) with the @@ -3066,8 +3144,8 @@ entry: make everything ``` -For more help on compiling entries, see also [3.0 - What Makefile rules are -available to build or clean up IOCCC entries?](#make_rules). +For more help on compiling entries, see also the +FAQ on "[IOCCC Makefile rules](#make_rules)". Of course in this case you can also switch to individual entries and look at the `index.html` file (or any other file in the entry) and try out the entries that @@ -3298,7 +3376,8 @@ some cases, such as `1984/mullender`, the original code is the same as the code as no changes were made (there is an alt version for systems that are not VAX-11/PDP-11, however). -See also [FAQ 4.2: What was changed in an IOCCC entry source code?](#what_changed) +See also +FAQ on "[entry source code changes](#what_changed)"
@@ -3381,8 +3460,9 @@ There were certainly other reasons as well. Like with files being renamed, there are multiple reasons files were added or removed. The addition of the `try.sh` and `try.alt.sh` scripts is the most -significant example of files being added. These scripts, as the [FAQ about this -says](#try), help demonstrate entries by automating commands, sometimes many +significant example of files being added. These scripts, as the +FAQ on "[try.sh and try.alt.sh](#try)", +help demonstrate entries by automating commands, sometimes many commands and not always simple commands, that one would previously have to run manually (there are other benefits as well). @@ -3417,7 +3497,9 @@ The [known bugs](bugs.html) file, order by IOCCC years, contains a list of known bugs & (mis)features. If you are looking for an IOCCC entry to try and fix, this file is a good place to start. -See [FAQ 5.2](#fix_an_entry) for information on how to submit a fix to +See +FAQ on "[fixing an entry](#fix_an_entry)" +for information on how to submit a fix to an IOCCC entry. Before you consider trying to fix an IOCCC winning entry, please check the [known bugs](bugs.html) file for the IOCCC entry in question. Note that in several cases what you may have discovered, @@ -3448,10 +3530,11 @@ fix. If it is accepted we'll be happy to credit you in the [thanks](thanks-for-help.html) file. If you're a previous author of a winning IOCCC entry we will happily link to your entries; if you're not we can link to your website if you wish. -Please see [FAQ 5.2 How may I submit a fix to an IOCCC -entry](#fix_an_entry) for information on how to submit a fix to an -IOCCC entry. See also the [FAQ 6.10 How does someone make a change -to a file and submit that change as a GitHub pull request](#pull_request) +Please see +FAQ on "[fixing an entry](#fix_an_entry)" +for information on how to submit a fix to an +IOCCC entry. See also the +FAQ on "[GitHub pull request](#pull_request)" for more information about pull requests. @@ -3494,10 +3577,11 @@ And of course, an IOCCC author may update their own entries against the [master branch](https://github.com/ioccc-src/winner/branches) of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner). -Please see [FAQ 5.2 How may I submit a fix to an IOCCC -entry](#fix_an_entry). See also the [FAQ 6.10 How does someone -make a change to a file and submit that change as a GitHub pull -request](#pull_request) for more information about pull requests. +Please see +FAQ on "[fixing an entry](#fix_an_entry)". +See also the +FAQ on "[GitHub pull request](#pull_request)" +for more information about pull requests. Note that we're much more inclined to accept an author's fixes but the judges have the final say in the matter. @@ -3510,14 +3594,18 @@ have the final say in the matter.
If you discover a problem with the IOCCC website that is related -to a particular IOCCC entry, please see [FAQ 5.1](#report_bug) for -information about reporting a bug in an IOCCC entry, and see [FAQ -5.2](#fix_an_entry) for information on how to submit a fix to an IOCCC entry. +to a particular IOCCC entry, please see +FAQ on "[report entry bug](#report_bug)" +for information about reporting a bug in an IOCCC entry, and see +FAQ on "[fixing an entry](#fix_an_entry)" +for information on how to submit a fix to an IOCCC entry. If you discover a problem with the IOCCC website (such as a broken link, which may or may not be specific to a particular IOCCC entry) that is **not related to a particular IOCCC entry**, the best way you can help is to submit a fix to -the IOCCC website. See [FAQ 5.4](#fix_web_site) for information on submitting fixes +the IOCCC website. See +FAQ on "[fixing the website](#fix_web_site)" +for information on submitting fixes to the IOCCC website. If you do not have an IOCCC website fix, and just wish to report a general IOCCC @@ -3535,17 +3623,20 @@ to [open a new IOCCC issue](https://github.com/ioccc-src/winner/issues/new).
For IOCCC website problems that relate to a particular IOCCC entry, please -see [FAQ 5.2](#fix_an_entry) for information on how submit a fix to an IOCCC entry. +see +FAQ on "[fixing an entry](#fix_an_entry)" +for information on how submit a fix to an IOCCC entry. You may open a [GitHub pull request](https://github.com/ioccc-src/winner/pulls) against the [master branch](https://github.com/ioccc-src/winner/branches) of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner) to submit a fix. -Please see [FAQ 5.2 How may I submit a fix to an IOCCC -entry](#fix_an_entry). See also the [FAQ 6.10 How does someone -make a change to a file and submit that change as a GitHub pull -request](#pull_request) for more information about pull requests. +Please see +FAQ on "[fixing an entry](#fix_an_entry)". +See also the +FAQ on "[GitHub pull request](#pull_request)" +for more information about pull requests. #### Some HTML files should NOT be directly modified @@ -3576,15 +3667,17 @@ For example, in [contact.html](contact.html), one may read: ``` This means that you could consider editing the referenced markdown file -AND then run `make www` from the top level directory in your [IOCCC pull -request](#pull_request). There are quicker ways but to be sure you get +AND then run `make www` from the top level directory in your IOCCC pull +request. There are quicker ways but to be sure you get everything built you should do this. If you modified a markdown and you do not see the same file as a html file then you did not complete the fix. -Please see [FAQ 5.2 How may I submit a fix to an IOCCC -entry](#fix_an_entry). See also the [FAQ 6.10 How does someone -make a change to a file and submit that change as a GitHub pull -request](#pull_request) for more information about pull requests. +Please see +FAQ on "[fixing an entry](#fix_an_entry)". + +See also the +FAQ on "[GitHub pull request](#pull_request)" +for more information about pull requests. In some cases, the HTML file is **NOT** based on markdown content, but instead came from JSON and other data files. So instead of the above reference to a @@ -3604,7 +3697,9 @@ This means there is **NOT even a markdown file to edit**. Instead one must modify JSON files and/or change a [bin directory tool](bin/index.html). If this happens, consider opening up an [IOCCC issue](https://github.com/ioccc-src/winner/issues) -and ask for help. See [FAQ 5.3](#fix_an_entry) for information on opening up an IOCCC issue. +and ask for help. See +FAQ on "[fixing an entry](#fix_an_entry)" +for information on opening up an IOCCC issue.
@@ -3620,9 +3715,13 @@ If you know the location of an author listed under:       **[ZZ - Unknown location](location.html#ZZ)** or if you find IOCCC author location that is incorrect, -then **please [submit a pull request](faq.html#pull_request)**, +then **please submit a pull request**, or at least [inform the IOCCC judges](contact.html). +See the +FAQ on "[GitHub pull request](#pull_request)" +for more information. + Authors of IOCCC winning entries are kept in JSON files of the form: ``` @@ -3631,19 +3730,25 @@ Authors of IOCCC winning entries are kept in JSON files of the form: where `author_handle` is an author handle. -See [FAQ 6.5](#author_handle_faq) for more information about author handles. +See the +FAQ on "[author handle](#author_handle_faq)" +for more information about author handles. -See [FAQ 6.6](#author_json) for information about the contents of these JSON file and -how they are used. +See the +FAQ on "[author_handle.json](#author_json)" +for information about the contents of these JSON file and how they are used. -See [FAQ 6.13](#find_author_handle) for how to find your own _author_handle_. +See the +FAQ on "[finding author handles](#find_author_handle)" +for how to find your own _author_handle_. The contents of these JSON files contain the best known information -about authors of IOCCC entries. See [FAQ 6.6](#author_json) for information -about the contents of these JSON file and how they are used. +about authors of IOCCC entries. See +FAQ on "[author_handle.json](#author_json)" +for information about the contents of these JSON file and how they are used. You may update IOCCC author information in a `author_handle.json` file -by [submitting a pull request](faq.html#pull_request) +by [submitting a pull request](#pull_request) against the [master branch](https://github.com/ioccc-src/winner/branches) of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner). @@ -3692,11 +3797,12 @@ only worry about those two files. This greatly speeds things along. Once that command finishes a proper `git status` and `git diff` shows that everything is in order. In the end the safest way is to run `make www`, however. -Please see [FAQ 5.2 How may I submit a fix to an IOCCC entry?](#fix_an_entry). +Please see +FAQ on "[fixing an entry](#fix_an_entry)". -See also the [FAQ 6.10 How does someone -make a change to a file and submit that change as a GitHub pull -request](#pull_request) for more information about pull requests. +See also the +FAQ on "[GitHub pull request](#pull_request)" +for more information about pull requests. **FYI**: The [ZZ - Unknown location](location.html#ZZ) is used for historic winning authors whose location or country is not known, @@ -3720,11 +3826,12 @@ want to have the location known but not their name and/or other details. We would appreciate if you try to fix the broken (the link goes nowhere) or wrong (the link goes to something that clearly is not the original intent) web link. If wish to fix such links, you may open a GitHub pull request as described in -[FAQ 5.4](#fix_web_site). In the case of dead links or invalid links it doesn't matter +FAQ on "[fixing the website](#fix_web_site)". +In the case of dead links or invalid links it doesn't matter if it's a specific winner or not; the procedure is the same: open a pull request -to fix the problem. See also the [FAQ 6.10 How does someone -make a change to a file and submit that change as a GitHub pull -request](#pull_request) for more information about pull requests. +to fix the problem. See also the +FAQ on "[GitHub pull request](#pull_request)" +for more information about pull requests. As far as how to find the updated link you can try using the [Internet Wayback Machine](https://web.archive.org) and see if you can find the last non 4xx non @@ -3761,7 +3868,8 @@ replace that text with: See the **author's description of the program** (sorry the content is no longer available) for more information. ``` -If you just wish to report the bad link issue, see [FAQ 5.3](#report_web_problem). +If you just wish to report the bad link issue, see +FAQ on "[report website problem](#report_web_problem)".
@@ -3910,11 +4018,13 @@ we request that you ask the [IOCCC judges](judges.html) first. Please send your request using the instructions on the [contacting the IOCCC Judges](contact.html) page. -Please note that the content of the IOCCC is [Copyrighted and is under -the CC BY-SA 4.0 License](#copyright). +Please note that the content of the IOCCC +**Copyrighted and is under the CC BY-SA 4.0 License**. +See the [Copyright](#copyright) at the bottom of IOCCC web pages for more details. -See [FAQ 6.11](#license) for additional information on the -[Copyright and CC BY-SA 4.0 License](license.html). +See +FAQ on "[using IOCCC content](#license)". +For additional information on the [Copyright and CC BY-SA 4.0 License](license.html).
@@ -3972,13 +4082,19 @@ For each `author_handle`, there will be a JSON file of the form: author/author_handle.json ``` -See [FAQ 5.5](#fix_author) for information about how to update +See the +FAQ on "[fixing author information](#fix_author)" +for information about how to update and/or correct IOCCC author information. -See [FAQ 6.6](#author_json) for information about the contents of these JSON file and +See the +FAQ on "[.auth.json](#auth_json)" +for information about the contents of these JSON file and how they are used. -See [FAQ 6.13](#find_author_handle) for how to find your own _author_handle_. +See the +FAQ on "[finding author handle](#find_author_handle)" +for how to find your own _author_handle_. Because the `author_handle` is used to form a JSON filename, the string must be POSIX safe string plus the use of `+` (for technical reasons beyond this @@ -4060,8 +4176,9 @@ of the form: author/author_handle.json ``` -where _author_handle_ is an author handle. See [FAQ 6.5](#author_handle_faq) for more -information about an author handles. +where _author_handle_ is an author handle. See +FAQ on "[author handle](#author_handle_faq)" +for more information about an author handles. #### `author_handle.json` JSON file contents @@ -4215,7 +4332,9 @@ This _JSON member_ holds the author handle of the author. There **MUST** be one and only one `author_handle` _JSON member_ and the _JSON value_ **MUST** be a _JSON string_ that is also a value author handle. -See [FAQ 6.5](#author_handle_faq) for more information about an author handles. +See +FAQ on "[author handle](#author_handle_faq)" +for more information about an author handles. Normally the _author_handle_ _JSON value_ should **NOT** be changed **unless there is a strong reason to do so**. If the _JSON value_ @@ -4451,7 +4570,7 @@ be a _JSON string_ or it **MUST** be a _JSON null_. The _JSON string_ just be a If the `mastodon` handle is a _JSON null_, them the `mastodon_url` **MUST** be a _JSON null_. If the `mastodon` handle is a _JSON string_, then the `mastodon_url` **MUST** be a _JSON string_. -The `mastodon_url` is just a translation of the above mentioned [mastodon](#mastodon) handle. +The `mastodon_url` is just a translation of the above mentioned Mastodon handle. For example, if the Mastodon handle is: ``` @@ -4474,8 +4593,9 @@ For example: NOTE: The _JSON null_ is **NOT** enclosed in quotes! -See [the FAQ on what is Mastodon and why does IOCCC uses it](faq.html#try_mastodon) for more -information on Mastodon. +See +FAQ on "[Mastodon](#try_mastodon)" +for more information on Mastodon. ##### github @@ -4565,9 +4685,13 @@ is a valid entry ID. Due to the nature of the _So-called JSON spec_, the last value of the `winning_entry_set` _JSON array_ cannot end in a comma (_,_). -See [FAQ 6.7](#author_json) for information about entry ids. +See +FAQ on "[author_handle.json](#author_json)" +for information about entry ids. -See [FAQ 5.5](#fix_author) for information about how to update +See +FAQ on "[fixing author information](#fix_author)" +for information about how to update and/or correct IOCCC author information. @@ -5016,7 +5140,9 @@ by going to your entry in the [authors.html](authors.html) web page and viewing that follows the _author_handle_: line. If you are not someone who has won a previous IOCCC, you will be able to select -a potential _author_handle_ when you form your _submission_ tarball (see [FAQ 0.0](#submit)). +a potential _author_handle_ when you form your _submission_ tarball (see +FAQ on "[how to submit](#submit)" +). **Helpful Hint**: If an _author_ clicks on their _author_handle:_ line link, you will be taken to that author's `author_handle.json` file. @@ -5029,15 +5155,23 @@ the [Brian_Westley.json](%%REPO_URL%%/author/Brian_Westley.json) file. **IMPORTANT NOTE**: An `author` who has won a previous IOCCC is encouraged to reuse their `author_handle` so that new winning entries can be associated with the same author. -See [FAQ 5.5](#fix_author) for information about how to update +See +FAQ on "[fixing author information](#fix_author)" +for information about how to update and/or correct IOCCC author information. -See [FAQ 6.5](#author_handle_faq) for more information about author handles. +See +FAQ on "[author handle](#author_handle_faq)" +for more information about author handles. -See [FAQ 6.6](#author_json) for information about the contents of these JSON file and +See +FAQ on "[author_handle.json](#author_json)" +for information about the contents of these JSON file and how they are used. -See [FAQ 6.9](#terms) for more information on terms such as _author_, _entry_, and _submission_. +See +FAQ on "[Author, Entry, Submission](#terms)" +for more information on terms such as _author_, _entry_, and _submission_.
@@ -5080,8 +5214,8 @@ Simply move your mouse cursor over the category you want and then click on the item you wish to view that drops down from the category. This is likely how it will appear with a [tablet device in landscape -mode](faq.html#tablet_menu), too, unless [JavaScript is -disabled](faq.html#no_javascript_menu). +mode](#tablet_menu), too, unless [JavaScript is +disabled](#no_javascript_menu).
@@ -5134,11 +5268,11 @@ to . With tablets, it likely depends on the orientation you have your device in. If it's in portrait mode you likely will see the [menu that one will get on a mobile -phone](faq.html#mobile_phone_menu). +phone](#mobile_phone_menu). If, on the other hand, you are using landscape mode, say on an iPad Pro 11 inch 4th generation, then you will likely see the [menu as you would on a desktop or -laptop](faq.html#desktop_menu). +laptop](#desktop_menu).
@@ -5153,7 +5287,7 @@ very possibly have to **press and hold** the menu icon: width=24 height=24> to activate it. You can then use it [as you would on a mobile -phone](faq.html#mobile_phone_menu). +phone](#mobile_phone_menu).
@@ -5171,9 +5305,9 @@ Notice how the menu icon is not even there! This happens in both portrait mode and landscape mode. In this case one will have to use the [no JavaScript -menu](faq.html#no_javascript_menu). If you have a fix for this that **does NOT +menu](#no_javascript_menu). If you have a fix for this that **does NOT affect the usability of desktops, laptops or other mobile devices**, please -consider fixing it and [opening a pull request](faq.html#pull_request) or at +consider fixing it and [opening a pull request](#pull_request) or at least [report it as an issue](https://github.com/ioccc-src/temp-test-ioccc/issues/new/choose) (choose the category _Website issue_). diff --git a/index.html b/index.html index 0bb3078ad..f9891b69b 100644 --- a/index.html +++ b/index.html @@ -413,7 +413,8 @@ then consider making pull requests against the here. See also the FAQ on menus.

+here. See also the +FAQ on “website menus”.

Obfuscate defined:

tr.v. -cated, -cating, -cates.

@@ -434,7 +435,9 @@ plaintext menu even with JavaScript enabled, you can do so

Entering the Contest

View the current status of the IOCCC to see of the IOCCC is open for submissions.

-

See the FAQ about how to enter the IOCCC for more information.

+

See +FAQ on “how to submit” +for more information.

Important Disclaimer

IOCCC code is for educational and entertainment purposes only. We do NOT recommend installing any winning IOCCC entry code. Use code found the IOCCC repo and in the IOCCC web site at your own risk!

The IOCCC and the IOCCC judges DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THEY BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

diff --git a/index.md b/index.md index 2b3a949ea..17aea2a64 100644 --- a/index.md +++ b/index.md @@ -34,7 +34,8 @@ On a **touchscreen mobile device** browser **wider than 1024 pixels**, **press and hold** the menu you wish to activate (in the upper right corner) in order to activate the pull-down. If this does not work or you prefer to use a plaintext menu even with JavaScript enabled, you can do so -[here](nojs-menu.html). See also the [FAQ on menus](faq.html#menus). +[here](nojs-menu.html). See also the +FAQ on "[website menus](faq.html#menus)". # Obfuscate defined: @@ -64,7 +65,9 @@ The goals of the IOCCC: View the [current status of the IOCCC](status.html) to see of the IOCCC is open for submissions. -See [the FAQ about how to enter the IOCCC](faq.html#submit) for more information. +See +FAQ on "[how to submit](faq.html#submit)" +for more information. # Important Disclaimer diff --git a/markdown.html b/markdown.html index 37ad964f7..cbad7c3a3 100644 --- a/markdown.html +++ b/markdown.html @@ -390,14 +390,17 @@

IOCCC markdown guidelines

The IOCCC makes extensive use of markdown. -For example, when submitting to the IOCCC, we have people +For example, when submitting to the IOCCC +we have people submit remarks about their entry in markdown format. Every winning IOCCC entry uses a README.md markdown file as the basis for forming the index.html web page for that entry. All generated HTML pages on the Official IOCCC website start with some markdown content.

See the markdown syntax guide. -See also the CommonMark Spec.

+See also the CommonMark Spec. +See the +FAQ on “how to submit”.

Nevertheless, the IOCCC does have certain practices that we ask authors to follow. Some of these relate to use of markdown directly and others relate to injecting HTML into the markdown file.

diff --git a/markdown.md b/markdown.md index ec288b50b..f79e76992 100644 --- a/markdown.md +++ b/markdown.md @@ -1,7 +1,8 @@ # IOCCC markdown guidelines The IOCCC makes extensive use of [markdown](https://daringfireball.net/projects/markdown/). -For example, when [submitting to the IOCCC](faq.html#submit), we have people +For example, when submitting to the IOCCC +we have people submit remarks about their entry in markdown format. Every [winning IOCCC entry](years.html) uses a `README.md` markdown file as the basis for forming the `index.html` web page for that entry. @@ -10,6 +11,8 @@ start with some markdown content. See the [markdown syntax](https://www.markdownguide.org/basic-syntax) guide. See also the [CommonMark Spec](https://spec.commonmark.org/current/). +See the +FAQ on "[how to submit](faq.html#submit)". Nevertheless, the IOCCC does have certain practices that we ask authors to follow. Some of these relate to use of markdown directly and others relate to injecting HTML diff --git a/news.html b/news.html index dd1796763..b93eab6a2 100644 --- a/news.html +++ b/news.html @@ -392,8 +392,9 @@

Please follow the IOCCC on Mastodon

We use Mastodon to make minor announcements, in addition to announcing major events such as the opening of a new IOCCC, or who won.

-

See “FAQ 6.12: What is Mastodon and why does IOCCC use it?” for more -information on Mastodon.

+

See +FAQ on “Mastodon” +for more information on Mastodon.

News

2024-06-08

We continue to make good progress on the @@ -403,7 +404,7 @@ via the temp-test-ioccc has been checked for broken links which leaves two longer files to go. These two files are the bugs.html -file and the FAQ.

+file and the “IOCCC FAQ”.

However, where it was thought that those two files would be looked at before the other html files, it has been decided that they will be done after the other files as it is very possible that some things in these two files will have to be @@ -419,7 +420,7 @@ June 2024 have been checked for invalid links so that only new news updates will have to be checked.

Once those are done the html files of all the entries will be looked at. As those are being reviewed it the bugs.html might very well be -updated and the FAQ might be as well. This is why, as noted above, +updated and the “IOCCC FAQ” might be as well. This is why, as noted above, we have decided to review these files last, in order to save time and effort in not having to look at them more than once on a whole, other than possible entries that have to be added at the end, like the example below.

diff --git a/news.md b/news.md index ed22d1dd3..478452777 100644 --- a/news.md +++ b/news.md @@ -5,8 +5,9 @@ We use Mastodon to make minor announcements, in addition to announcing major events such as the opening of a new IOCCC, or who won. -See "[FAQ 6.12: What is Mastodon and why does IOCCC use it?](faq.html#try_mastodon)" for more -information on Mastodon. +See +FAQ on "[Mastodon](faq.html#try_mastodon)" +for more information on Mastodon.
# News @@ -22,7 +23,7 @@ One of the [largest html files](thanks-for-help.html) has been checked for broken links which leaves two longer files to go. These two files are the [bugs.html](bugs.html) -file and the [FAQ](faq.html). +file and the "[IOCCC FAQ](faq.html)". However, where it was thought that those two files would be looked at before the other html files, it has been decided that they will be done after the other @@ -41,7 +42,7 @@ will have to be checked. Once those are done the html files of all the entries will be looked at. As those are being reviewed it the [bugs.html](bugs.html) might very well be -updated and the [FAQ](faq.html) might be as well. This is why, as noted above, +updated and the "[IOCCC FAQ](faq.html)" might be as well. This is why, as noted above, we have decided to review these files last, in order to save time and effort in not having to look at them more than once on a whole, other than possible entries that have to be added at the end, like the example below. diff --git a/next/guidelines.html b/next/guidelines.html index 1a4ca761c..7799c46ba 100644 --- a/next/guidelines.html +++ b/next/guidelines.html @@ -395,9 +395,11 @@ and are VERY LIKELY to be updated before the next IOCCC. They are are provided as a VERY TENTATIVE hint at what MIGHT be used in the next IOCCC. In some cases they might even be a copy of the guidelines from the previous IOCCC.

-

See our FAQ about providing feedback as well -as our FAQ about asking questions about -these guidelines.

+

See our +FAQ on “rules, guidelines, tools feedback”. +as well as our +FAQ on “asking questions” +about these guidelines.

The IOCCC is closed

The IOCCC is NOT accepting new submissions at this time. See the IOCCC winning entries page for the entries that have won the @@ -476,8 +478,8 @@ The submit URL should be active on or slightly before 2024-MMM-DD HH:MM: The IOCCC rules, IOCCC guidelines will be available on the Official IOCCC website on or slightly before start of this IOCCC. Please check -the IOCCC FAQ about how to submit to see how -to submit entries, on or after the start of this IOCCC, to be sure +FAQ on “how to submit” +to see how to submit entries, on or after the start of this IOCCC, to be sure you are using the correct versions of these items before using the IOCCC submission URL.

@@ -672,8 +674,8 @@ below) fails to validate the .auth.json or .info.json it is an error and possibly a bug that you should report as a bug at the mkiocccentry issues page. -PLEASE run the bug_report.sh script to help us out here! See the the FAQ -about reporting bugs in the mkiocccentry repo. +PLEASE run the bug_report.sh script to help us out here! See the +FAQ on “report mkiocccentry bugs”.

However, just because there are errors does not mean it is a bug in the @@ -897,8 +899,8 @@ not pass and you used mkiocccentry(1) it is very possibly a bug and report it as a bug at the mkiocccentry issues page. -See the the FAQ about reporting -bugs in the mkiocccentry repo. +See the +FAQ on “report mkiocccentry bugs”.

Assuming that chkentry(1) validates both .auth.json and @@ -940,8 +942,8 @@ compressed tarball; if any issues are found (‘feathers are stuck in the mkiocccentry(1), then it is very possibly a bug in one of the tools and you should report it as a bug at the mkiocccentry issues page. PLEASE run the -bug_report.sh script to help us out here! See the FAQ about reporting bugs -in the mkiocccentry repo. +bug_report.sh script to help us out here! See +FAQ on “report mkiocccentry bugs”.

As part of its sanity checks, txzchk(1) will run fnamchk(1) on the @@ -955,8 +957,8 @@ would prevent this from happening as it would not create such a file anyway. If mkiocccentry(1) was used it would rather suggest a bug in one of the tools and you should report it as a bug at the mkiocccentry issues page. -See the FAQ about reporting bugs in the mkiocccentry -repo. +See +FAQ on “report mkiocccentry bugs”.

If verbosity level is > 0, txzchk(1) will show the contents of the tarball which is @@ -1045,8 +1047,9 @@ by modifying the CSTD Makefile variable. For example, to use 

    CSTD= -std=c17

For compilers, such as clang, that have the -Weverything option, -while you may wish to try it, you should look at the FAQ about clang --Weverything. We do NOT recommend that you put +while you may wish to try it, you should look at +FAQ on “clang -Weverything”. +We do NOT recommend that you put the use of -Weverything into your submission’s Makefile for the reasons cited there. This goes even if your version does not trigger a warning as some other version might! @@ -1884,7 +1887,8 @@ It has been shown that receiving anonymous gifts provides the IOCCC judges help make the IOCCC better for everyone. :-)

-See FAQ: How may I support the IOCCC?. +See +FAQ on “support the IOCCC”.

More often than not, we select a small submission (usually one line) and a strange/creative layout submission. We sometimes also select a @@ -1987,7 +1991,8 @@ See the Official IOCCC website news for additional in

For the updates and breaking IOCCC news, you are encouraged to follow the IOCCC on Mastodon. See our -FAQ on Mastodon for more information. Please be +FAQ on “Mastodon” +for more information. Please be aware that unless you are mentioned you most likely will NOT get a notification so you should make sure to check the page.

diff --git a/next/guidelines.md b/next/guidelines.md index 5a4d4da29..0f3c5282d 100644 --- a/next/guidelines.md +++ b/next/guidelines.md @@ -8,9 +8,11 @@ They are are provided as a **VERY TENTATIVE** hint at **what MIGHT** be used in the next IOCCC. In some cases they might even be a copy of the guidelines from the previous IOCCC. -See our [FAQ about providing feedback](../faq.html#feedback) as well -as our [FAQ about asking questions](../faq.html#question) about -these guidelines. +See our +FAQ on "[rules, guidelines, tools feedback](#feedback)". +as well as our +FAQ on "[asking questions](../faq.html#question)" +about these guidelines. # The IOCCC is closed @@ -115,8 +117,8 @@ The submit URL should be active on or slightly before **2024-MMM-DD HH:MM:SS UTC The [IOCCC rules](rules.html), [IOCCC guidelines](guidelines.html) will be available on the [Official IOCCC website](https://www.ioccc.org) on or slightly before start of this IOCCC. Please check -[the IOCCC FAQ about how to submit](../faq.html#submit) to see how -to submit entries, on or after the start of this IOCCC, to be sure +FAQ on "[how to submit](../faq.html#submit)" +to see how to submit entries, on or after the start of this IOCCC, to be sure you are using the correct versions of these items before using the IOCCC submission URL.

@@ -354,8 +356,8 @@ below) fails to validate the `.auth.json` or `.info.json` it is an error and possibly a bug that you should [report as a bug at the mkiocccentry issues page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E). -**PLEASE run the `bug_report.sh` script to help us out here!** See the [the FAQ -about reporting bugs in the mkiocccentry repo](../faq.html#mkiocccentry_bugs). +**PLEASE run the `bug_report.sh` script to help us out here!** See the +FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".

@@ -558,8 +560,8 @@ not pass and you used `mkiocccentry(1)` it is very possibly a bug and you should [report it as a bug at the mkiocccentry issues page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E). -See the [the FAQ about reporting -bugs in the mkiocccentry repo](../faq.html#mkiocccentry_bugs). +See the +FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".

@@ -613,8 +615,8 @@ tarball`' :-) ) **AND if and _ONLY IF_ you used `mkiocccentry(1)`**, then it is very possibly a bug in one of the tools and you should [report it as a bug at the mkiocccentry issues page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E). **PLEASE run the -`bug_report.sh` script to help us out here!** See [the FAQ about reporting bugs -in the mkiocccentry repo](../faq.html#mkiocccentry_bugs). +`bug_report.sh` script to help us out here!** See +FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".

@@ -630,8 +632,8 @@ would prevent this from happening as it would not create such a file anyway. If `mkiocccentry(1)` was used it would rather suggest a bug in one of the tools and you should [report it as a bug at the mkiocccentry issues page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E). -See [the FAQ about reporting bugs in the mkiocccentry -repo](../faq.html#mkiocccentry_bugs). +See +FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".

@@ -753,8 +755,9 @@ by modifying the `CSTD` Makefile variable. For example, to use `c17` instead:

For compilers, such as `clang`, that have the `-Weverything` option, -while you may wish to try it, you should look at [the FAQ about clang --Weverything](../faq.html#weverything). We do **NOT** recommend that you put +while you may wish to try it, you should look at +FAQ on "[clang -Weverything](../faq.html#weverything)". +We do **NOT** recommend that you put the use of `-Weverything` into your submission's `Makefile` for the reasons cited there. This goes even if your version does not trigger a warning as some other version might! @@ -1768,7 +1771,8 @@ It has been shown that receiving **anonymous** gifts provides the

-See [FAQ: How may I support the IOCCC?](../faq.html#support). +See +FAQ on "[support the IOCCC](../faq.html#support)".

More often than not, we select a small submission (usually one line) and a @@ -1903,7 +1907,8 @@ See the [Official IOCCC website news](../news.html) for additional information.

For the updates and breaking [IOCCC news](../news.html), you are encouraged to follow the [IOCCC on Mastodon](https://fosstodon.org/@ioccc). See our -[FAQ on Mastodon](../faq.html#try_mastodon) for more information. **Please be +FAQ on "[Mastodon](../faq.html#try_mastodon)" +for more information. **Please be aware** that unless you are mentioned you most likely will **NOT** get a notification so you should make sure to check the page.

diff --git a/next/rules.html b/next/rules.html index aad391070..6180ebe9c 100644 --- a/next/rules.html +++ b/next/rules.html @@ -395,9 +395,11 @@ and are VERY LIKELY to be updated before the next IOCCC. They are are provided as a VERY TENTATIVE hint at what MIGHT be used in the next IOCCC. In some cases they might even be a copy of the rules from the previous IOCCC.

-

See our FAQ about providing feedback as well -as our FAQ about asking questions about -these rules.

+

See our +FAQ on “rules, guidelines, tools feedback”. +as well as our +FAQ on “about asking questions” +about these rules.

The IOCCC is closed

The IOCCC is NOT accepting new submissions at this time. See the IOCCC winning entries page for the entries that have won the @@ -472,7 +474,8 @@ provisional BETA versions and may be adjusted AT AN

When the IOCCC is open, the submission URL is: https://submit.ioccc.org; at all other times that link is likely to be unresponsive.

-

Please check the How to enter FAQ +

Please check the +FAQ on “how to submit” for important information on how to submit to the IOCCC.

The submit URL should be active on or slightly before 2024-MMM-DD HH:MM:SS UTC.
@@ -482,7 +485,7 @@ The submit URL should be active on or slightly before 2024-MMM-DD HH:MM:

The official IOCCC rules and IOCCC guidelines will be available on the official IOCCC website on or slightly before the start of this IOCCC. The mkiocccentry toolkit may be obtained at any time -at the mkiocccentry repo.

+at the report mkiocccentry bugs.

Please recheck on or after the start of this IOCCC to be sure you are using the correct versions of these items before using the IOCCC submission URL.

@@ -570,7 +573,8 @@ as a command like argument to the iocccsize(1) tool. For example:

Rule 3

Submissions should be performed using the instructions outlined at: -the How to enter FAQ.

+the +FAQ on “how to submit”

To submit to an open IOCCC, you must use the IOCCC submit server. Unless the IOCCC is open, that link will likely be unresponsive.

@@ -696,8 +700,9 @@ In order to register for the IOCCC, you MUST have a valid email enough time for one automated exchange of email as part of your submission.

-See the FAQ on how to register for the IOCCC in the -FAQ for details. +See +FAQ on “how to register” +for details.

Rule 16

@@ -824,14 +829,18 @@ those requirements. The Makefile MUST be a non-empty file in GNU Makefile form. See the Makefile.example, -the FAQ about your submission’s Makefile and -the FAQ about IOCCC Makefile compatibility for help. +the +FAQ on “submission Makefile” +and the +FAQ on “Makefile compatibility” +for help.

The remarks.md MUST be a non-empty file in markdown form. See also -Rule 18 and our FAQ about what to put in your -remarks.md and the FAQ about IOCCC best markdown -practices. +Rule 18 and our +FAQ on “remarks.md” +and the +FAQ on “markdown practices”.

See also the markdown syntax guide @@ -957,8 +966,8 @@ If you run into a problem with one or more of these tools, PLEASE, making sure to run bug_report.sh. See the guidelines -for help here and also read the FAQ about reporting bugs in the mkiocccentry -repo. +for help here and also read +FAQ on “mkiocccentry repo bugs”.

At the risk of stating the obvious: submissions that violate Rule @@ -991,8 +1000,7 @@ Basics. We currently use pandoc to convert markdown to HTML.

-Please see our FAQ about what to put in your -remarks.md and the IOCCC markdown +Please see our FAQ “remarks.md” and the IOCCC markdown guidelines for additional markdown guidance.

@@ -1104,7 +1112,8 @@ You should be sure you have the current IOCCC rules and

For the updates and breaking IOCCC news, you are encouraged to follow the IOCCC on Mastodon account. See our -FAQ about Mastodon for more information. Please do note that unless +FAQ on “Mastodon” +for more information. Please do note that unless you are mentioned by us you will NOT get a notification from the app so you should refresh the page even if you do follow us.

diff --git a/next/rules.md b/next/rules.md index 9a040f8e1..b95faeb67 100644 --- a/next/rules.md +++ b/next/rules.md @@ -8,9 +8,11 @@ They are are provided as a **VERY TENTATIVE** hint at **what MIGHT** be used in the next IOCCC. In some cases they might even be a copy of the rules from the previous IOCCC. -See our [FAQ about providing feedback](../faq.html#feedback) as well -as our [FAQ about asking questions](../faq.html#question) about -these rules. +See our +FAQ on "[rules, guidelines, tools feedback](#feedback)". +as well as our +FAQ on "[about asking questions](../faq.html#question)" +about these rules. # The IOCCC is closed @@ -112,7 +114,8 @@ When the IOCCC is open, the submission URL is: [https://submit.ioccc.org](https://submit.ioccc.org); at all other times that link is likely to be unresponsive. -Please check the [How to enter FAQ](../faq.html#submit) +Please check the +FAQ on "[how to submit](../faq.html#submit)" for **important information** on how to submit to the IOCCC.

@@ -125,7 +128,7 @@ Please wait to submit your entries until after that time. The official [IOCCC rules](rules.html) and [IOCCC guidelines](guidelines.html) will be available on the [official IOCCC website](../index.html) on or slightly before the start of this IOCCC. The `mkiocccentry` toolkit may be obtained at any time -at the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry). +at the [report mkiocccentry bugs](https://github.com/ioccc-src/mkiocccentry). **Please recheck on or after the start of this IOCCC to be sure you are using the correct versions of these items _before using the IOCCC @@ -249,7 +252,8 @@ as a command like argument to the `iocccsize(1)` tool. For example:

Submissions should be performed using the instructions outlined at: -the [How to enter FAQ](../faq.html#submit). +the +FAQ on "[how to submit](../faq.html#submit)" To submit to an open IOCCC, you must use the [IOCCC submit server](https://submit.ioccc.org/). Unless the IOCCC is open, that link will @@ -429,8 +433,9 @@ enough time for one automated exchange of email as part of your submission.

-See [the FAQ on how to register for the IOCCC](../faq.html#register) in the -[FAQ](../faq.html) for details. +See +FAQ on "[how to register](../faq.html#register)" +for details.

@@ -554,15 +559,19 @@ those requirements. The `Makefile` **MUST** be a **non**-empty file in **[GNU Makefile](https://www.gnu.org/software/make/manual/make.html)** form. See the [Makefile.example](https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example), -the [FAQ about your submission's Makefile](../faq.html#submission_makefiles) and -the [FAQ about IOCCC Makefile compatibility](../faq.html#make_compatibility) for help. +the +FAQ on "[submission Makefile](../faq.html#submission_makefiles)" +and the +FAQ on "[Makefile compatibility](../faq.html#make_compatibility)" +for help.

The `remarks.md` **MUST** be a **non**-empty file in markdown form. See also -[Rule 18](#rule18) and our [FAQ about what to put in your -remarks.md](../faq.html#remarks_md) and the [FAQ about IOCCC best markdown -practices](../faq.html#markdown). +[Rule 18](#rule18) and our +FAQ on "[remarks.md](../faq.html#remarks_md)" +and the +FAQ on "[markdown practices](../faq.html#markdown)".

@@ -690,8 +699,8 @@ If you run into a problem with one or more of these tools, **PLEASE** [report it as a bug at the mkiocccentry issues page](https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E), **making sure to run `bug_report.sh`**. See the [guidelines](guidelines.html) -for help here and also read [the FAQ about reporting bugs in the mkiocccentry -repo](../faq.html#mkiocccentry_bugs). +for help here and also read +FAQ on "[mkiocccentry repo bugs](../faq.html#mkiocccentry_bugs)".

At the risk of stating the obvious: submissions that violate [Rule @@ -735,8 +744,7 @@ We currently use [pandoc](https://pandoc.org) to convert markdown to HTML.

-Please see our [FAQ about what to put in your -remarks.md](../faq.html#remarks_md) and the [IOCCC markdown +Please see our FAQ "[remarks.md](../faq.html#remarks_md)" and the [IOCCC markdown guidelines](../markdown.html) for additional markdown guidance.

@@ -890,7 +898,8 @@ See the [Official IOCCC website news](../news.html) for additional information.

For the updates and breaking IOCCC news, you are encouraged to follow the [IOCCC on Mastodon](https://fosstodon.org/@ioccc) account. See our -[FAQ about Mastodon](../faq.html#try_mastodon) for more information. Please do note that unless +FAQ on "[Mastodon](../faq.html#try_mastodon)" +for more information. Please do note that unless you are mentioned by us you will **NOT** get a notification from the app _so you should refresh the page **even if you do follow us**_.

diff --git a/status.html b/status.html index 2d3a03dda..00b5b8f80 100644 --- a/status.html +++ b/status.html @@ -431,7 +431,10 @@ Comments and suggestions on these preliminary items are welcome. See the IOCCC news for details including the tentative scheduled opening date.

“open”

-

The IOCCC is open for submissions.

+

The IOCCC is open for submissions.

+

See the +FAQ on “how to submit” +for more information.

See the IOCCC news page for details on rules, guidelines, tools and deadlines.

Be sure to review the official IOCCC rules, guidelines, and tools for any changes that may have been made while the IOCCC was @@ -458,8 +461,7 @@ winning entries page.

  • Update the IOCCC news page.

    • “closed”

    -

    The IOCCC is closed and is NOT accepting new -submissions.

    +

    The IOCCC is closed and is NOT accepting submissions.

    See the IOCCC winning entries page for the entries that have won the IOCCC.

    NOTE: From time to time, winning IOCCC entries may have their write-ups updated, @@ -467,6 +469,9 @@ the IOCCC.

    Watch both this IOCCC status page and the @IOCCC mastodon feed for information about future IOCCC openings.

    +

    See the +FAQ on “how to submit” +for more information on the submission process when the IOCCC reopens.

    news_update

    This shows the latest modification date for the IOCCC news page.

    The JSON member value is a JSON quoted string obtained from the date field diff --git a/status.md b/status.md index 635c5b32b..9541d1831 100644 --- a/status.md +++ b/status.md @@ -54,7 +54,11 @@ scheduled opening date. #### "**open**"

    -The [IOCCC](index.html) is [open](#open) for [submissions](faq.html#submit). +The [IOCCC](index.html) is [open](#open) for submissions. + +See the +FAQ on "[how to submit](faq.html#submit)" +for more information. See the [IOCCC news](news.html) page for details on rules, guidelines, tools and deadlines. @@ -96,8 +100,7 @@ winning entries page](years.html). #### "**closed**" -The [IOCCC](index.html) is closed and is **NOT** accepting [new -submissions](faq.html#submit). +The [IOCCC](index.html) is closed and is **NOT** accepting submissions. See the [IOCCC winning entries page](years.html) for the entries that have won the [IOCCC](index.html). @@ -109,6 +112,10 @@ Watch both [this IOCCC status page](status.html) and the [@IOCCC mastodon feed](https://fosstodon.org/@ioccc) for information about future [IOCCC](index.html) [openings](#open). +See the +FAQ on "[how to submit](faq.html#submit)" +for more information on the submission process when the IOCCC reopens. +
    ## news_update diff --git a/thanks-for-help.html b/thanks-for-help.html index 4da166988..2915ac897 100644 --- a/thanks-for-help.html +++ b/thanks-for-help.html @@ -549,9 +549,9 @@ returning to the shell. The original code does not have this change.

    versions of clang object to the number of args of main(), saying that it must be 0, 2 or 3. The version this has been observed in does not actually object to 1 arg but it is entirely possible that this changes so a second arg (that’s not -needed and is unused) has been added just in case. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +needed and is unused) has been added just in case. See +FAQ on “main function args” +for more details.

    Cody also added the script primes.sh which allows one to check the output for the first N prime numbers of the output, where N is either the default or user specified. The inspiration was the previous try @@ -682,10 +682,10 @@ should they object to main() having only one arg.

    Winning entry: 1986/hague

    Winning entry source code: hague.c

    -

    Cody made this use fgets(). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    -

    Cody also added the try.sh script which also feeds to the +

    Cody made this use fgets(). See +FAQ on “gets and fgets” +for why this was done. +Cody also added the try.sh script which also feeds to the program the input.txt text file that Cody added.

    Winning entry: 1986/holloway

    @@ -894,9 +894,9 @@ size constraints of the contest).

    Winning entry: 1987/wall

    Winning entry source code: wall.c

    -

    Cody made this use fgets(3). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    +

    Cody made this use fgets(3). See +FAQ on “gets and fgets” +for why this was done.

    Cody also added the try.sh script.

    Winning entry: 1987/westley

    @@ -1009,9 +1009,9 @@ same code, just a p instead of an m in the name. Addit

    Winning entry: 1988/reddy

    Winning entry source code: reddy.c

    -

    Cody made this use fgets(3). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    +

    Cody made this use fgets(3). See +FAQ on “gets and fgets” +for why this was done.

    Winning entry: 1988/spinellis

    Winning entry source code: spinellis.c

    @@ -1270,9 +1270,9 @@ judges was retained.

    Yusuke got this to work in modern systems (it previously resulted in a bus error).

    -

    Cody made this use fgets(3). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    +

    Cody made this use fgets(3). See +FAQ on “gets and fgets” +for why this was done.

    Winning entry: 1990/dds

    Winning entry source code: dds.c

    @@ -1285,9 +1285,9 @@ more like the original in this way by redefining free to have the c operator itself.

    Cody fixed another compiler error by removing the erroneous prototype to fopen(3). Cody also changed a char * used for file I/O to be a proper FILE * and fixed a typo in LANDER.BAS.

    -

    Cody also made this use fgets(3). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    +

    Cody also made this use fgets(3). See +FAQ on “gets and fgets” +for why this was done.

    Winning entry: 1990/dg

    Winning entry source code: dg.c

    @@ -1347,9 +1347,9 @@ author.

    Cody also changed the code (in both versions) to use fgets(3) instead of gets(3) so one would not get a warning about the use of gets(3) at linking time or execution, the latter of which was causing confusing output due to the -warning being interspersed with the program’s interactive output. See FAQ 4.1 -- Why were some calls to the libc function gets(3) changed to use -fgets(3)? for more details on why this change was +warning being interspersed with the program’s interactive output. See +FAQ on “gets and fgets” +for more details on why this change was done more generally.

    Winning entry: 1990/theorem

    @@ -1370,9 +1370,9 @@ but as he was testing the fibonacci.c bug he ended up changing it a 
        if (a[1]==NULL||a[2]==NULL||a[3]==NULL||a[4]==NULL||a[5]==NULL) return 1;

    be changed to just test the value of A when a is argv and A is argc? You tell us!

    -

    Cody also changed the code to use fgets(3). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    +

    Cody also changed the code to use fgets(3). See +FAQ on “gets and fgets” +for why this was done.

    Since this program is so incredible the extra fixes were deemed worth having and this is why they were done.

    Cody later disabled a warning in the Makefile that proved to be a problem only @@ -1481,9 +1481,9 @@ being a problem not being declared first, to hopefully future-proof it.

    condition (the char *s had to be changed to char s[]) and he also made it and the generated code work for clang.

    Furthermore Cody changed it so that the C from the BASIC uses fgets(), not -gets(). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    +gets(). See +FAQ on “gets and fgets” +for why this was done.

    For the magic of clang (which was done manually except the returning a value in main() in the generated code and possibly fgets(3)) and fgets(3), see below. The problem with clang can be described simply as: clang (at least in @@ -1643,9 +1643,9 @@ true of another change as further below.

    + putc(i["}|uutsrq`_^bji`[Zkediml[PO]a_M__]ISOYIRGTNR"]+i-9,stderr);

    though it’s questionable how much more (if at all) obscure that is :-)

    Cody also changed the location that it used gets() to be fgets(3). -See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done. +See +FAQ on “gets and fgets” +for why this was done. This was complicated because of how the other source files are generated (as above); simply changing the code could cause invalid output in the program which made other files fail to compile (for this example specifically, see below).

    @@ -1770,9 +1770,9 @@ start and end character.

    defect with the number of args to main() though when it comes to 1 arg it is only in an error message if say 4 args are used. This is out of an abundance of caution as it’s quite possible that clang or the ANSI C committee end up further -changing this. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +changing this. See +FAQ on “main function args” +for more details.

    Yusuke also noted that there is a bug in the program where right after starting it moves towards the right but if you click the mouse it goes back. See 1992/kivinen in bugs.html for more details.

    @@ -1785,9 +1785,9 @@ it works (see Judges’ remarks in file) this will not work with clang.

    Cody also provided the lush.sh script to demonstrate it as using make was problematic.

    -

    Cody made it use fgets() instead of gets(). See FAQ 4.1 - Why were some calls to -the libc function gets)3( changed to use -fgets(3)? for why this was done.

    +

    Cody made it use fgets() instead of gets(). See +FAQ on “gets and fgets” +for why this was done.

    NOTE: this entry cannot work with clang due to different compiler messages (it will compile fine but it won’t work). See 1992/lush in bugs.html for details.

    @@ -1959,9 +1959,9 @@ compile time. See the index.html for details.

    Winning entry: 1993/schnitzi

    Winning entry source code: schnitzi.c

    -

    Cody made this use fgets(3) not gets(3). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    +

    Cody made this use fgets(3) not gets(3). See +FAQ on “gets and fgets” +for why this was done.

    Winning entry: 1993/vanb

    Winning entry source code: vanb.c

    @@ -2050,9 +2050,9 @@ comma operator was needed.

    type (because time(2) takes a time_t * which in some systems is a long * but what was being passed to it is an int).

    Cody also changed the entry to use fgets(3) instead of gets(3). -(See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.)

    +(See +FAQ on “gets and fgets” +for why this was done.)

    This one has a minor annoyance in that it now prints a newline after the output but this seems like a worthy compromise for preventing the interspersed output in macOS @@ -2113,9 +2113,9 @@ remarks), FAQ 4.1 - Why were some calls to -the libc function gets)3( changed to use -fgets(3)? for why this was done. +See +FAQ on “gets and fgets” +]for why this was done. In this case the newline had to be terminated but it was a pretty straightforward fix. gets() was defined to use fgets() and the inclusion of stdio.h had to be added but to make it @@ -2164,9 +2164,9 @@ details on this.

    type of args. In particular some versions supposedly only allow 0, 2 or 3 args. It actually appears to allow 1 but if you specify 4 it says 0, 2 or 3 and it is an error but it’s entirely possible that they will eventually make the defect -function as the error message claims. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +function as the error message claims. See +FAQ on “main function args” +for more details.

    Winning entry: 1995/dodsond1

    Winning entry source code: dodsond1.c

    @@ -2381,9 +2381,9 @@ versions of clang whine about the number of args on top of what typ In particular some versions claim that they only allow 0, 2 or 3 args. It appears that they do allow 1 but for instance 4 is not allowed. However as it’s quite possible they will ‘fix’ this defect it would be better to have this not -be a problem at such a time. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +be a problem at such a time. See +FAQ on “main function args” +for more details.

    Cody also added the bas1.sh script to simplify running the program.

    @@ -2451,9 +2451,9 @@ versions of clang complain about the number of args to main() claim that only 0, 2 or 3 are allowed but it does allow 1 anyway. It is quite possible though that this will change so it is fixed in case this happens. As it is mostly just through the C pre-processor Cody added a new macro to make the -code look like the original with just an extra arg. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +code look like the original with just an extra arg. See +FAQ on “main function args” +for more details.

    In some versions of clang -Wno-int-conversion had to be added to the CSILENCE variable of the Makefile.

    Cody also added the try.sh script to show the output of some @@ -2550,9 +2550,9 @@ occurs.

    Cody made main() have two args out of an abundance of caution as some versions of clang say that main() can only have 0, 2 or 3 args. These versions accept 1 arg but it is entirely possible that they fix this so this should prevent it -from breaking if that happens. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +from breaking if that happens. See +FAQ on “main function args” +for more details.

    Cody added the try.sh script to make it easier to try the commands that we suggested. One command was not added, that of the to use command.

    @@ -2589,9 +2589,9 @@ commands that we recommended.

    Winning entry source code: anderson.c

    Cody changed this entry to use fgets(3) instead of gets(3). -See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done. +See +FAQ on “gets and fgets” +for why this was done. This involved changing the K arg to gets(3) to &K in fgets(3).

    Cody also added the try.sh script.

    @@ -3082,9 +3082,9 @@ a lot of numbers this will be harder to see).

    discovered it will not work otherwise.

    Cody, out of an abundance of caution for clang, added a second arg to main() as some versions complain about the number of args and although they accept 1 it -is entirely possible it will eventually be that they don’t. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +is entirely possible it will eventually be that they don’t. See +FAQ on “main function args” +for more details.

    Cody also added the try.sh script and various data files: kopczynski-a to demonstrate what happens when art more like a letter is fed to the program and the kopczynski*-rev files which are @@ -3107,9 +3107,9 @@ chose the word IOCCC instead of AAA).

    Winning entry: 2004/schnitzi

    Winning entry source code: schnitzi.c

    -

    Cody made this use fgets(3). See FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)? for why this was done.

    +

    Cody made this use fgets(3). See +FAQ on “gets and fgets” +for why this was done.

    He also changed the time factor in the data files as the animations went too fast in modern systems, especially the scrolling text of schnitzi.inp1.

    @@ -3472,9 +3472,9 @@ it to the repo as well.

    Cody, out of an abundance of caution for clang’s defects, made main() have 2 args instead of 1 as some versions report that main() must have 0, 2 or 3 -args, even though at least one of those versions allows 1 arg only. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +args, even though at least one of those versions allows 1 arg only. See +FAQ on “main function args” +for more details.

    Cody also added the try.sh script for easier use of the entry to show the clock update in real time.

    @@ -3530,9 +3530,9 @@ We’re not able to test this.

    Cody, out of an abundance of caution, added a second arg to main() as some versions of clang complain about not only the type of each arg to main() but -the number of args as well. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +the number of args as well. See +FAQ on “main function args” +for more details.

    Cody also added the try.sh script.

    Winning entry: 2011/dlowe

    @@ -3702,9 +3702,9 @@ everything, filtered through less.

    Cody also changed argv to be not const char ** but char **, mostly out of an abundance of caution in case clang, which already imposes restrictions on the types of args to main() including to do with char **, decides to further -restrict them. See FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries? for more details.

    +restrict them. See +FAQ on “main function args” +for more details.

    Cody also restored the original code from the archive.

    And although the URL works for now (via redirect), Cody changed the website linked to in the recipe file to the domain that the old one currently redirects @@ -3918,8 +3918,8 @@ also appear to be an issue with the script even if you know of convertCody added the try.sh script.

    Cody also (out of an abundance of caution for clang(1) which is strict with arg type and count to main()) added a second (unused) arg to main(). See -FAQ 4.6 - Why was arg count and/or type changed in main() in some -older entries? for more details.

    +FAQ on “main function args” +for more details.

    Winning entry: 2013/endoh4

    Winning entry source code: endoh4.c

    @@ -4272,9 +4272,9 @@ the repo.

    some versions of clang object to the number of args of main(), saying that it must be 0, 2 or 3. The version this has been observed in does not actually object to 1 arg but it is entirely possible that this changes so a second arg -(that’s not needed and is unused) has been added just in case. See FAQ 4.6 - -Why was arg count and/or type changed in main() in some older -entries? for more details.

    +(that’s not needed and is unused) has been added just in case. See +FAQ on “main function args” +for more details.

    Cody also added explicit linking of libm (-lm) for systems that do not do this (Linux doesn’t seem to but macOS does).

    Cody also added alternate code that should diff --git a/thanks-for-help.md b/thanks-for-help.md index ba6575530..12a942e18 100644 --- a/thanks-for-help.md +++ b/thanks-for-help.md @@ -217,9 +217,9 @@ returning to the shell. The original code does not have this change. versions of `clang` object to the number of args of `main()`, saying that it must be 0, 2 or 3. The version this has been observed in does not actually object to 1 arg but it is entirely possible that this changes so a second arg (that's not -needed and is unused) has been added just in case. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +needed and is unused) has been added just in case. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Cody also added the script [primes.sh](%%REPO_URL%%/1985/august/primes.sh) which allows one to check the output for the first `N` prime numbers of the output, where `N` is @@ -403,10 +403,9 @@ Cody also added the [try.sh](%%REPO_URL%%/1985/sicherman/try.sh) and ### Winning entry source code: [hague.c](%%REPO_URL%%/1986/hague/hague.c)

    -[Cody](#cody) made this use `fgets()`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. - +[Cody](#cody) made this use `fgets()`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. Cody also added the [try.sh](%%REPO_URL%%/1986/hague/try.sh) script which also feeds to the program the `input.txt` text file that Cody added. @@ -724,9 +723,9 @@ size constraints of the contest). ### Winning entry source code: [wall.c](%%REPO_URL%%/1987/wall/wall.c)
    -[Cody](#cody) made this use `fgets(3)`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +[Cody](#cody) made this use `fgets(3)`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. Cody also added the [try.sh](%%REPO_URL%%/1987/wall/try.sh) script. @@ -890,9 +889,9 @@ same code, just a `p` instead of an `m` in the name. Additionally, `main()` retu ### Winning entry source code: [reddy.c](%%REPO_URL%%/1988/reddy/reddy.c)
    -[Cody](#cody) made this use `fgets(3)`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +[Cody](#cody) made this use `fgets(3)`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. @@ -1247,9 +1246,9 @@ judges was retained. [Yusuke](#yusuke) got this to work in modern systems (it previously resulted in a bus error). -[Cody](#cody) made this use `fgets(3)`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +[Cody](#cody) made this use `fgets(3)`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. @@ -1270,9 +1269,9 @@ Cody fixed another compiler error by removing the erroneous prototype to `fopen(3)`. Cody also changed a `char *` used for file I/O to be a proper `FILE *` and fixed a typo in [LANDER.BAS](%%REPO_URL%%/1990/dds/LANDER.BAS). -Cody also made this use `fgets(3)`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +Cody also made this use `fgets(3)`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. @@ -1361,9 +1360,9 @@ author. Cody also changed the code (in both versions) to use `fgets(3)` instead of `gets(3)` so one would not get a warning about the use of `gets(3)` at linking time or execution, the latter of which was causing confusing output due to the -warning being interspersed with the program's interactive output. See [FAQ 4.1 -- Why were some calls to the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for more details on why this change was +warning being interspersed with the program's interactive output. See +FAQ on "[gets and fgets](faq.html#gets)" +for more details on why this change was done more generally. @@ -1394,9 +1393,9 @@ BTW: why can't the fix: be changed to just test the value of `A` when `a` is argv and `A` is argc? You tell us! -Cody also changed the code to use `fgets(3)`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +Cody also changed the code to use `fgets(3)`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. Since this program is so incredible the extra fixes were deemed worth having and @@ -1545,9 +1544,9 @@ condition (the `char *s` had to be changed to `char s[]`) and he also made it and the generated code work for `clang`. Furthermore Cody changed it so that the C from the BASIC uses `fgets()`, not -`gets()`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +`gets()`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. For the magic of `clang` (which was done manually except the returning a value in `main()` in the generated code and possibly `fgets(3)`) and `fgets(3)`, see @@ -1799,9 +1798,9 @@ Cody also restored a slightly more obscure line of code that had been changed: though it's questionable how much more (if at all) obscure that is :-) Cody also changed the location that it used `gets()` to be `fgets(3)`. -See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. This was complicated because of how the other source files are generated (as above); simply changing the code could cause invalid output in the program which made other files fail to compile (for this example specifically, see below). @@ -1970,9 +1969,9 @@ Cody made `main()` have two args, not one, as some versions of `clang` have a defect with the number of args to `main()` though when it comes to 1 arg it is only in an error message if say 4 args are used. This is out of an abundance of caution as it's quite possible that `clang` or the ANSI C committee end up further -changing this. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +changing this. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Yusuke also noted that there is a bug in the program where right after starting @@ -1992,9 +1991,9 @@ file](1992/lush/index.html#judges-remarks)) this will not work with `clang`. [Cody](#cody) also provided the [lush.sh](%%REPO_URL%%/1992/lush/lush.sh) script to demonstrate it as using make was problematic. -Cody made it use `fgets()` instead of `gets()`. See [FAQ 4.1 - Why were some calls to -the libc function gets)3( changed to use -fgets(3)?](faq.html#gets) for why this was done. +Cody made it use `fgets()` instead of `gets()`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. NOTE: this entry cannot work with `clang` due to different compiler messages (it will compile fine but it won't work). See [1992/lush in @@ -2232,9 +2231,9 @@ compile time. See the index.html for details. ### Winning entry source code: [schnitzi.c](%%REPO_URL%%/1993/schnitzi/schnitzi.c)
    -[Cody](#cody) made this use `fgets(3)` not `gets(3)`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +[Cody](#cody) made this use `fgets(3)` not `gets(3)`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. @@ -2359,9 +2358,9 @@ type (because `time(2)` takes a `time_t *` which in some systems is a `long *` but what was being passed to it is an `int`). Cody also changed the entry to use `fgets(3)` instead of `gets(3)`. -(See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done.) +(See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done.) This one has a minor annoyance in that it now prints a newline after the output but this @@ -2440,9 +2439,9 @@ each mode allowed with two sizes, 128 and 256, allowing one to quit or skip each (given that there are a lot of invocations this seemed like a good idea). Cody also made this use `fgets(3)` instead of `gets(3)`. -See [FAQ 4.1 - Why were some calls to -the libc function gets)3( changed to use -fgets(3)?](faq.html#gets) for why this was done. +See +FAQ on "[gets and fgets](faq.html#gets)" +]for why this was done. In this case the newline had to be terminated but it was a pretty straightforward fix. `gets()` was defined to use `fgets()` and the inclusion of `stdio.h` had to be added but to make it @@ -2506,9 +2505,9 @@ Out of an abundance of caution with `clang`, Cody also added a second arg to type of args. In particular some versions supposedly only allow 0, 2 or 3 args. It actually appears to allow 1 but if you specify 4 it says 0, 2 or 3 and it is an error but it's entirely possible that they will eventually make the defect -function as the error message claims. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +function as the error message claims. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. @@ -2808,9 +2807,9 @@ versions of `clang` whine about the number of args on top of what type they are In particular some versions claim that they only allow 0, 2 or 3 args. It appears that they do allow 1 but for instance 4 is not allowed. However as it's quite possible they will 'fix' this defect it would be better to have this not -be a problem at such a time. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +be a problem at such a time. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Cody also added the [bas1.sh](%%REPO_URL%%/1998/bas1/bas1.sh) script to simplify running the @@ -2906,9 +2905,9 @@ versions of `clang` complain about the number of args to `main()`. These version claim that only 0, 2 or 3 are allowed but it does allow 1 anyway. It is quite possible though that this will change so it is fixed in case this happens. As it is mostly just through the C pre-processor Cody added a new macro to make the -code look like the original with just an extra arg. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +code look like the original with just an extra arg. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. In some versions of `clang` `-Wno-int-conversion` had to be added to the @@ -3046,9 +3045,9 @@ occurs. Cody made `main()` have two args out of an abundance of caution as some versions of `clang` say that `main()` can only have 0, 2 or 3 args. These versions accept 1 arg but it is entirely possible that they fix this so this should prevent it -from breaking if that happens. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +from breaking if that happens. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Cody added the [try.sh](%%REPO_URL%%/1998/schweikh3/try.sh) script to make it easier to try @@ -3104,9 +3103,9 @@ commands that we recommended.
    [Cody](#cody) changed this entry to use `fgets(3)` instead of `gets(3)`. -See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. This involved changing the `K` arg to `gets(3)` to `&K` in `fgets(3)`. Cody also added the [try.sh](%%REPO_URL%%/2000/anderson/try.sh) script. @@ -3798,9 +3797,9 @@ discovered it will not work otherwise. Cody, out of an abundance of caution for `clang`, added a second arg to `main()` as some versions complain about the number of args and although they accept 1 it -is entirely possible it will eventually be that they don't. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +is entirely possible it will eventually be that they don't. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Cody also added the [try.sh](%%REPO_URL%%/2004/kopczynski/try.sh) script and various data files: [kopczynski-a](%%REPO_URL%%/2004/kopczynski/kopczynski-a) to demonstrate what happens when art more @@ -3834,9 +3833,9 @@ chose the word `IOCCC` instead of `AAA`). ### Winning entry source code: [schnitzi.c](%%REPO_URL%%/2004/schnitzi//schnitzi.c)
    -[Cody](#cody) made this use `fgets(3)`. See [FAQ 4.1 - Why were some calls to -the libc function gets(3) changed to use -fgets(3)?](faq.html#gets) for why this was done. +[Cody](#cody) made this use `fgets(3)`. See +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. He also changed the time factor in the data files as the animations went too @@ -4354,9 +4353,9 @@ it to the repo as well. [Cody](#cody), out of an abundance of caution for `clang`'s defects, made `main()` have 2 args instead of 1 as some versions report that `main()` must have 0, 2 or 3 -args, even though at least one of those versions allows 1 arg only. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +args, even though at least one of those versions allows 1 arg only. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Cody also added the [try.sh](%%REPO_URL%%/2006/sykes2/try.sh) script for easier use of the @@ -4438,9 +4437,9 @@ We're not able to test this. [Cody](#cody), out of an abundance of caution, added a second arg to `main()` as some versions of `clang` complain about not only the type of each arg to `main()` but -the number of args as well. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +the number of args as well. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Cody also added the [try.sh](%%REPO_URL%%/2011/borsanyi/try.sh) script. @@ -4679,9 +4678,9 @@ Cody also fixed a typo in the ruby script Cody also changed `argv` to be not `const char **` but `char **`, mostly out of an abundance of caution in case `clang`, which already imposes restrictions on the types of args to `main()` including to do with `char **`, decides to further -restrict them. See [FAQ 4.6 - Why was arg -count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +restrict them. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Cody also restored the original code from the archive. @@ -4974,8 +4973,8 @@ The entry can still be enjoyed if you do not have these tools, however. Cody also (out of an abundance of caution for `clang(1)` which is strict with arg type and count to `main()`) added a second (unused) arg to `main()`. See -[FAQ 4.6 - Why was arg count and/or type changed in main() in some -older entries?](faq.html#arg_count) for more details. +FAQ on "[main function args](faq.html#arg_count)" +for more details. @@ -5489,9 +5488,9 @@ Cody also, out of abundance of caution, added a second arg to `main()` because some versions of `clang` object to the number of args of `main()`, saying that it must be 0, 2 or 3. The version this has been observed in does not actually object to 1 arg but it is entirely possible that this changes so a second arg -(that's not needed and is unused) has been added just in case. See [FAQ 4.6 - -Why was arg count and/or type changed in main() in some older -entries?](faq.html#arg_count) for more details. +(that's not needed and is unused) has been added just in case. See +FAQ on "[main function args](faq.html#arg_count)" +for more details. Cody also added explicit linking of libm (`-lm`) for systems that do not do this