From 89e66b96c5dd652f8c13bb789da28561b8a42ce7 Mon Sep 17 00:00:00 2001 From: Landon Curt Noll Date: Sun, 21 Jul 2024 16:17:20 -0700 Subject: [PATCH] improve word flow around FAQ references --- 1993/jonth/README.md | 2 +- 2000/thadgavin/README.md | 2 +- 2000/thadgavin/index.html | 2 +- 2005/boutines/README.md | 2 +- 2005/boutines/index.html | 2 +- 2005/jetro/README.md | 2 +- 2005/jetro/index.html | 2 +- 2012/zeitak/README.md | 5 +- 2012/zeitak/index.html | 4 +- 2013/endoh3/README.md | 2 +- 2013/endoh3/index.html | 2 +- 2014/maffiodo1/README.md | 2 +- 2014/maffiodo1/index.html | 2 +- 2015/endoh1/README.md | 2 +- 2015/endoh1/index.html | 2 +- 2018/algmyr/README.md | 2 +- 2018/algmyr/index.html | 2 +- 2018/bellard/README.md | 4 +- 2018/bellard/index.html | 4 +- 2018/giles/README.md | 2 +- 2018/giles/index.html | 2 +- 2018/poikola/README.md | 2 +- 2018/poikola/index.html | 2 +- 2019/giles/README.md | 2 +- 2019/giles/index.html | 2 +- 2020/giles/README.md | 2 +- 2020/giles/index.html | 2 +- contact.html | 22 +++---- contact.md | 22 +++---- faq.html | 55 +++++++++-------- faq.md | 56 +++++++++-------- index.html | 2 +- index.md | 2 +- news.html | 2 +- news.md | 2 +- next/guidelines.html | 10 +-- next/guidelines.md | 12 ++-- next/rules.html | 11 ++-- next/rules.md | 11 ++-- thanks-for-help.html | 105 +++++++++++++++++++------------ thanks-for-help.md | 127 ++++++++++++++++++++++++++------------ 41 files changed, 289 insertions(+), 213 deletions(-) diff --git a/1993/jonth/README.md b/1993/jonth/README.md index 6b4fcf793..300ffc340 100644 --- a/1993/jonth/README.md +++ b/1993/jonth/README.md @@ -1,7 +1,7 @@ ## To build: NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to -compile. See the +compile. See the FAQ on "[X11](../../faq.html#X11)" if you need help. diff --git a/2000/thadgavin/README.md b/2000/thadgavin/README.md index 9247bbb21..ec021e25a 100644 --- a/2000/thadgavin/README.md +++ b/2000/thadgavin/README.md @@ -7,7 +7,7 @@ NOTE: if you don't have curses or SDL1 installed both modes will fail to compile. In that case see the FAQ on "[SDL1 and SDL2](../../faq.html#SDL)" -and +and the FAQ on "[ncurses](../../faq.html#curses)" for more information. diff --git a/2000/thadgavin/index.html b/2000/thadgavin/index.html index caf9445d9..9f97e1062 100644 --- a/2000/thadgavin/index.html +++ b/2000/thadgavin/index.html @@ -417,7 +417,7 @@ Location: GB - United Kingdom of Great

NOTE: if you don’t have curses or SDL1 installed both modes will fail to compile. In that case see the FAQ on “SDL1 and SDL2” -and +and the FAQ on “ncurses” for more information.

We recommend that you use the alternate code so you can see what this entry diff --git a/2005/boutines/README.md b/2005/boutines/README.md index 357e8b76d..c6f276a43 100644 --- a/2005/boutines/README.md +++ b/2005/boutines/README.md @@ -9,7 +9,7 @@ You will need an [SVG](https://www.w3.org/TR/SVG11/expanded-toc.html) viewer or a converter like [ImageMagick](https://imagemagick.org/index.php)'s `convert`. -See +See the FAQ on "[ImageMagick](../../faq.html#imagemagick)". Look here to find some [SVG Viewer diff --git a/2005/boutines/index.html b/2005/boutines/index.html index 0905c3cc8..65ececb62 100644 --- a/2005/boutines/index.html +++ b/2005/boutines/index.html @@ -412,7 +412,7 @@ Location: FR - French Republic (To use:

You will need an SVG viewer or a converter like ImageMagick’s convert. -See +See the FAQ on “ImageMagick”.

Look here to find some SVG Viewer Implementations.

diff --git a/2005/jetro/README.md b/2005/jetro/README.md index d15f67545..189248101 100644 --- a/2005/jetro/README.md +++ b/2005/jetro/README.md @@ -1,6 +1,6 @@ ## To build: -This entry requires SDL. See +This entry requires SDL. See the FAQ on "[SDL1 and SDL2](../../faq.html#SDL)" for information on how to install it if you haven't already. diff --git a/2005/jetro/index.html b/2005/jetro/index.html index 523752159..9c33be895 100644 --- a/2005/jetro/index.html +++ b/2005/jetro/index.html @@ -408,7 +408,7 @@ Location: FI - Republic of Finland

To build:

-

This entry requires SDL. See +

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

diff --git a/2012/zeitak/README.md b/2012/zeitak/README.md index 71c0770b9..afb684a90 100644 --- a/2012/zeitak/README.md +++ b/2012/zeitak/README.md @@ -64,8 +64,9 @@ NOTE: if you use vim to view the code, make sure to do: :set tabstop=4 ``` -in command mode, before looking at the code, to see the correct layout. For more -help see the +in command mode, before looking at the code, to see the correct layout. + +For more help, see the FAQ on "[tabstops](../../faq.html#tabstops)". diff --git a/2012/zeitak/index.html b/2012/zeitak/index.html index d6c65b47c..91035846c 100644 --- a/2012/zeitak/index.html +++ b/2012/zeitak/index.html @@ -437,8 +437,8 @@ minutes just to understand 18 key characters of this code.

NOTE: if you use vim to view the code, make sure to do:

    :set tabstop=4
-

in command mode, before looking at the code, to see the correct layout. For more -help see the +

in command mode, before looking at the code, to see the correct layout.

+

For more help, see the FAQ on “tabstops”.

Author’s remarks:

Nesting Errors Detector

diff --git a/2013/endoh3/README.md b/2013/endoh3/README.md index cc0c713d4..25335232c 100644 --- a/2013/endoh3/README.md +++ b/2013/endoh3/README.md @@ -20,7 +20,7 @@ For more detailed information see [2013/endoh3 in bugs.html](../../bugs.html#201 ./endoh3 ``` -This program plays sound. See +This program plays sound. See the FAQ on "[compile with sound](../../faq.html#sox)" if you do not know how to set your system up for this or if you want to verify that everything is oky. diff --git a/2013/endoh3/index.html b/2013/endoh3/index.html index 395db964d..7f0b57c45 100644 --- a/2013/endoh3/index.html +++ b/2013/endoh3/index.html @@ -417,7 +417,7 @@ Location: JP - Japan

For more detailed information see 2013/endoh3 in bugs.html.

To use:

    ./endoh3
-

This program plays sound. See +

This program plays sound. See the FAQ on “compile with sound” if you do not know how to set your system up for this or if you want to verify that everything is oky.

diff --git a/2014/maffiodo1/README.md b/2014/maffiodo1/README.md index 98d2199c0..f275f462a 100644 --- a/2014/maffiodo1/README.md +++ b/2014/maffiodo1/README.md @@ -1,6 +1,6 @@ ## To build: -This entry requires SDL to be installed. See +This entry requires SDL to be installed. See the FAQ on "[SDL1 and SDL2](../../faq.html#SDL)" if you don't know how to do this for your system. diff --git a/2014/maffiodo1/index.html b/2014/maffiodo1/index.html index fadf9ec03..f3fc5889a 100644 --- a/2014/maffiodo1/index.html +++ b/2014/maffiodo1/index.html @@ -408,7 +408,7 @@ Location: IT - Italian Republic (<

To build:

-

This entry requires SDL to be installed. See +

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

    make
diff --git a/2015/endoh1/README.md b/2015/endoh1/README.md index 5f95d5e6f..8d1f6e24a 100644 --- a/2015/endoh1/README.md +++ b/2015/endoh1/README.md @@ -5,7 +5,7 @@ ``` NOTE: this program requires the tool `tcpserver` to use. If you do not have this -program see +program see the FAQ on "[tcpserver](../../faq.html#tcpserver)". diff --git a/2015/endoh1/index.html b/2015/endoh1/index.html index f6ce38f68..ba3cef160 100644 --- a/2015/endoh1/index.html +++ b/2015/endoh1/index.html @@ -415,7 +415,7 @@ Location: JP - Japan

To build:

    make

NOTE: this program requires the tool tcpserver to use. If you do not have this -program see +program see the FAQ on “tcpserver”.

To use:

    tcpserver -v 127.0.0.1 10333 ./prog ioccc.txt
diff --git a/2018/algmyr/README.md b/2018/algmyr/README.md index aa428f11b..38a3724a6 100644 --- a/2018/algmyr/README.md +++ b/2018/algmyr/README.md @@ -5,7 +5,7 @@ ``` To use this entry requires, in some invocations, a sound processing program. -This can be ALSA or SoX but we recommend the latter. See +This can be ALSA or SoX but we recommend the latter. See the FAQ on "[SDL1 and SDL2](../../faq.html#sox)". diff --git a/2018/algmyr/index.html b/2018/algmyr/index.html index 1990f06d0..b3d5a2567 100644 --- a/2018/algmyr/index.html +++ b/2018/algmyr/index.html @@ -410,7 +410,7 @@ Location: SE - Kingdom of Sweden (

To build:

    make

To use this entry requires, in some invocations, a sound processing program. -This can be ALSA or SoX but we recommend the latter. See +This can be ALSA or SoX but we recommend the latter. See the FAQ on “SDL1 and SDL2”.

Bugs and (Mis)features:

The current status of this entry is:

diff --git a/2018/bellard/README.md b/2018/bellard/README.md index 3be2d4eab..60fab4f94 100644 --- a/2018/bellard/README.md +++ b/2018/bellard/README.md @@ -27,9 +27,9 @@ graphics viewer of choice. After that try: NOTE: the script uses the tools `pngtopam(1)` (or `pngtopnm(1)` for older versions) and `pnmscale` come from the netpbm project and `cjpeg(1)` comes from -`libjpeg-turbo`. If you don't have these tools already see +`libjpeg-turbo`. If you don't have these tools already see the FAQ on "[netpbm](../../faq.html#netpbm)" -and +and the FAQ on "[libjpeg-turbo](../../faq.html#libjpeg)". NOTE: [Lenna.png](Lenna.png) is from diff --git a/2018/bellard/index.html b/2018/bellard/index.html index d507d69fd..533daa416 100644 --- a/2018/bellard/index.html +++ b/2018/bellard/index.html @@ -420,9 +420,9 @@ graphics viewer of choice. After that try:

    ./try.sh

NOTE: the script uses the tools pngtopam(1) (or pngtopnm(1) for older versions) and pnmscale come from the netpbm project and cjpeg(1) comes from -libjpeg-turbo. If you don’t have these tools already see +libjpeg-turbo. If you don’t have these tools already see the FAQ on “netpbm” -and +and the FAQ on “libjpeg-turbo”.

NOTE: Lenna.png is from https://upload.wikimedia.org/wikipedia/en/7/7d/Lenna_%28test_image%29.png.

diff --git a/2018/giles/README.md b/2018/giles/README.md index c394636a5..e3b365226 100644 --- a/2018/giles/README.md +++ b/2018/giles/README.md @@ -1,6 +1,6 @@ ## To build: -This entry requires SDL2 to be installed. See +This entry requires SDL2 to be installed. See the FAQ on "[SDL1 and SDL2](../../faq.html#SDL)" if you don't have it installed and don't know how to do so. diff --git a/2018/giles/index.html b/2018/giles/index.html index b418d8b31..a0b719759 100644 --- a/2018/giles/index.html +++ b/2018/giles/index.html @@ -408,7 +408,7 @@ Location: AU - Commonwealth of Australi

To build:

-

This entry requires SDL2 to be installed. See +

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

diff --git a/2018/poikola/README.md b/2018/poikola/README.md index a11e35fd7..05b5ae0a0 100644 --- a/2018/poikola/README.md +++ b/2018/poikola/README.md @@ -96,7 +96,7 @@ best viewing experience is achieved when the terminal in use supports 24-bit colors, has a black background and the size is at least 125x38. Special note for Mac users: `Terminal.app` does not work as expected; you might -need xterm from XQuartz, see +need xterm from XQuartz, see the FAQ on "[X11 on macOS](../../faq.html#X11macos)", or some other working terminal. Thanks to [Dave Burton](../../authors.html#Dave_Burton) for spotting this diff --git a/2018/poikola/index.html b/2018/poikola/index.html index 5c5196854..07a96473a 100644 --- a/2018/poikola/index.html +++ b/2018/poikola/index.html @@ -454,7 +454,7 @@ better with it.

best viewing experience is achieved when the terminal in use supports 24-bit colors, has a black background and the size is at least 125x38.

Special note for Mac users: Terminal.app does not work as expected; you might -need xterm from XQuartz, see +need xterm from XQuartz, see the FAQ on “X11 on macOS”, or some other working terminal. Thanks to Dave Burton for spotting this diff --git a/2019/giles/README.md b/2019/giles/README.md index 46d4441b8..a8acbec3e 100644 --- a/2019/giles/README.md +++ b/2019/giles/README.md @@ -20,7 +20,7 @@ NOTE: `play`, which [try.sh](%%REPO_URL%%/2019/giles/try.sh) uses, comes from SoX, the Swiss Army Knife -of sound processing programs. If you don't have this installed, see +of sound processing programs. If you don't have this installed, see the FAQ on "[SDL1 and SDL2](../../faq.html#sox)". diff --git a/2019/giles/index.html b/2019/giles/index.html index fd753ed38..9b00b5e43 100644 --- a/2019/giles/index.html +++ b/2019/giles/index.html @@ -414,7 +414,7 @@ Location: AU - Commonwealth of Australi

Try:

    ./try.sh

NOTE: play, which try.sh uses, comes from SoX, the Swiss Army Knife -of sound processing programs. If you don’t have this installed, see +of sound processing programs. If you don’t have this installed, see the FAQ on “SDL1 and SDL2”.

Judges’ remarks:

Do you need to pretend enjoying a more spacious living environment than you diff --git a/2020/giles/README.md b/2020/giles/README.md index d4184112e..3dc16fe7e 100644 --- a/2020/giles/README.md +++ b/2020/giles/README.md @@ -40,7 +40,7 @@ will be converted to the DTMF sound! ``` If the script [try.sh](%%REPO_URL%%/2020/giles/try.sh) did not play a WAV file, it means you do not have -SoX installed; see +SoX installed; see the FAQ on "[SDL1 and SDL2](../../faq.html#sox)". In this case install it and try it again or play the files `jenny.wav` and `ioccc28.wav` in a program that can play WAV diff --git a/2020/giles/index.html b/2020/giles/index.html index 2e5bd2c9f..6ccdb52fe 100644 --- a/2020/giles/index.html +++ b/2020/giles/index.html @@ -431,7 +431,7 @@ will be converted to the DTMF sound!

# See ./prog 867-5309 > jenny.wav

If the script try.sh did not play a WAV file, it means you do not have -SoX installed; see +SoX installed; see the FAQ on “SDL1 and SDL2”. In this case install it and try it again or play the files jenny.wav and ioccc28.wav in a program that can play WAV diff --git a/contact.html b/contact.html index 8fa79845e..432f306df 100644 --- a/contact.html +++ b/contact.html @@ -391,13 +391,13 @@

WAIT!!! - Before you send that email

If you are trying to:

    -
  • Fix a winning IOCCC entry - See +
  • Fix a winning IOCCC entry - See our FAQ on “fix entry”
    • -
  • Update winning author information - See +
  • Update winning author information - See our FAQ on “fixing author information”
    • -
  • Correct a website problem - See +
  • Correct a website problem - See our FAQ on “fixing the website” -or +or our FAQ on “fix URL”

Instead of sending us email, Please consider using the GitHub @@ -406,11 +406,11 @@ against the master branch of the ioccc-src/winner repo.

If you are trying to:

    -
  • Report a bug in an IOCCC winning entry - See +
  • Report a bug in an IOCCC winning entry - See our FAQ on “report entry bug”
    • -
  • Report an IOCCC website problem - See +
  • Report an IOCCC website problem - See our FAQ on “report website problem”
    • -
  • Report a broken or wrong web link - See +
  • Report a broken or wrong web link - See our FAQ on “report broken link”

In general, unless you have a fix, if you want to report something, you should instead first look at the IOCCC @@ -421,11 +421,11 @@ reported, then feel free to rules feedback” -

  • Comment or make a suggestion on IOCCC guidelines - See +
  • Comment or make a suggestion on IOCCC guidelines - See our FAQ on “guidelines feedback”
    • -
  • Comment or make a suggestion on IOCCC tools - See +
  • Comment or make a suggestion on IOCCC tools - See our FAQ on “tools feedback”

    • Those FAQ entries will help guide you on how to make public comments @@ -437,7 +437,7 @@ and suggestion in the relevant places.

    Please follow the IOCCC on Mastodon

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

    -

    See +

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

    If you really need to send email the IOCCC judges

    diff --git a/contact.md b/contact.md index 1bb666579..a6d5efd86 100644 --- a/contact.md +++ b/contact.md @@ -2,13 +2,13 @@ If you are trying to: -* **Fix a winning IOCCC entry** - See +* **Fix a winning IOCCC entry** - See our FAQ on "[fix entry](faq.html#fix_an_entry)" -* **Update winning author information** - See +* **Update winning author information** - See our FAQ on "[fixing author information](faq.html#fix_author)" -* **Correct a website problem** - See +* **Correct a website problem** - See our FAQ on "[fixing the website](faq.html#fix_web_site)" -or +or our FAQ on "[fix URL](faq.html#fix_link)" Instead of sending us email, **Please** consider using the [GitHub @@ -18,11 +18,11 @@ of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner). If you are trying to: -* **Report a bug in an IOCCC winning entry** - See +* **Report a bug in an IOCCC winning entry** - See our FAQ on "[report entry bug](faq.html#report_bug)" -* **Report an IOCCC website problem** - See +* **Report an IOCCC website problem** - See our FAQ on "[report website problem](faq.html#report_web_problem)" -* **Report a broken or wrong web link** - See +* **Report a broken or wrong web link** - See our FAQ on "[report broken link](faq.html#fix_link)" In general, unless you have a fix, if you want to report something, you should instead first look at the [IOCCC @@ -34,11 +34,11 @@ issue](https://github.com/ioccc-src/winner/issues/new). If you are trying to: -* **Comment or make a suggestion on IOCCC rules** - See +* **Comment or make a suggestion on IOCCC rules** - See our FAQ on "[rules feedback](faq.html#feedback)" -* **Comment or make a suggestion on IOCCC guidelines** - See +* **Comment or make a suggestion on IOCCC guidelines** - See our FAQ on "[guidelines feedback](faq.html#feedback)" -* **Comment or make a suggestion on IOCCC tools** - See +* **Comment or make a suggestion on IOCCC tools** - See our FAQ on "[tools feedback](faq.html#feedback)" Those FAQ entries will help guide you on how to make public comments @@ -56,7 +56,7 @@ See the above FAQ entries for more details. We use Mastodon to make minor announcements, in addition announcing major events such as the opening of a new IOCCC, or who won. -See +See the FAQ on "[Mastodon](faq.html#try_mastodon)" for more information on Mastodon. diff --git a/faq.html b/faq.html index e375d0b5a..47fc28b81 100644 --- a/faq.html +++ b/faq.html @@ -545,7 +545,7 @@ to our submission portal.

  • Makefile

    Makefile to build (make all) and cleanup (make clean & make clobber)

  • remarks.md

    -

    Remarks about your entry in markdown format: see +

    Remarks about your entry in markdown format: see the FAQ on “remarks.md” for more info.

  • [file …]

    @@ -585,7 +585,7 @@ winners based on the same theme.

    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 +of your remarks.md file, see the FAQ on “remarks.md”, why you are submitting a entry based on a frequently submitted theme and how compares with previous IOCCC winners @@ -665,7 +665,7 @@ previous IOCCC entries make it more challenging to be successful.

    state something along the lines of:

        We tend to dislike programs that: are similar to previous winning entries.

    FAIR WARNING: Be sure to clearly explain near the beginning -of your remarks.md file, see +of your remarks.md file, see the FAQ on “remarks.md”, why you are submitting a entry based on a frequently submitted theme and how compares with previous IOCCC winners @@ -792,7 +792,7 @@ with your submission. If the IOCCC judges truly need m 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 +

    See also the FAQ on “rules, guidelines, tools feedback”.

    @@ -874,7 +874,7 @@ for a list of valid codes.

  • mastodon (null or double quoted string)

    • The Mastodon handle of this author in the form of @user@domain, or -null if not provided. See +null if not provided. See the FAQ on “Mastodon” for more information.
    • @@ -912,9 +912,9 @@ by this author.

    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 page and the author JSON file. -See +See the FAQ on “author handle” -and +and the FAQ on “author_handle.json” for more information.

  • author_number (number)

    @@ -1047,7 +1047,7 @@ array your submission will be invalid.

  • formed_timestamp (number)

    • Seconds since epoch when .auth.json was formed (seegettimeofday(2)`). -See also +See also the FAQ on “.info.json” for more inforation.
    @@ -1118,7 +1118,7 @@ the mandatory remarks.md file, and the mandatory C source file. See the FAQ on “.auth.json” -and +and the FAQ on “remarks.md” for more inforation.

      @@ -2031,7 +2031,7 @@ 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 +the spirit of the original code are very welcome! Please see the FAQ on “fixing an entry” for details. See also the FAQ on “GitHub pull request” @@ -2048,7 +2048,7 @@ others will be looked at, when found.

      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 +Please see the FAQ on “fixing an entry” for details.

      @@ -2068,7 +2068,7 @@ other things that have to be done plus remembering to do it.

      See if the problem is mentioned in 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 +form of a pull request. Please see the FAQ on “fixing an entry”. See also the FAQ on “GitHub pull request” @@ -2155,7 +2155,7 @@ for more information.

      provide alternate code that works for Wayland. We will happily credit you in the thanks-for-help.html file.

      Red Hat based Linux

      -

      First, see +

      First, see the FAQ on “general X11”.

      Install Xorg and related packages:

          sudo dnf install --skip-broken --best --exclude xorgxrdp --exclude xorgxrdp-glamor '*xorg*' 'libx*' 'libX*' 'fontconfig*'
      @@ -2490,7 +2490,7 @@ that you may wish to try.

      entry. If so, you are invited to try and fix the IOCCC entry and submit that fix by way of a GitHub pull request. -Please see +Please see the FAQ on “fixing an entry” for how to submit a fix to an IOCCC entry.

      @@ -2629,7 +2629,7 @@ for downloading, installing and using ImageMagick.

      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 +

      In general OpenGL needs X11 to be installed and the X Window Server to be running. See the FAQ on “X11” for general information about X11.

      Once X11 is install and the X Window Server is running, one needs to compile @@ -2939,7 +2939,7 @@ original code is in entry source code changes”

      FAQ 4.4: What is the meaning of the file ending in .orig.c in IOCCC entries?

      @@ -3003,10 +3003,13 @@ other times something else.

      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 on “try.sh and try.alt.sh”, +try.sh sometimes the try.alt.sh scripts 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).

      +

      See the +FAQ on “try.sh and try.alt.sh” +for more details.

      Alternate code, sometimes provided by the author, sometimes provided by the judges and sometimes other people, was added to some entries as well.

      In the case that a link might end up with a 404 the files, if possible, were @@ -3028,7 +3031,7 @@ ways.

      The known bugs 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 +

      See the FAQ on “fixing an entry” for information on how to submit a fix to an IOCCC entry. Before you consider trying to fix an IOCCC winning entry, @@ -3054,7 +3057,7 @@ course if the entry does not work we’ll certainly be more inclined to accept t fix. If it is accepted we’ll be happy to credit you in the thanks 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 +

      Please see the FAQ on “fixing an entry” for information on how to submit a fix to an IOCCC entry. See also the @@ -3091,7 +3094,7 @@ IOCCC winning entries are presented!

      GitHub pull request against the master branch of the ioccc-src/winner repo.

      -

      Please see +

      Please see the FAQ on “fixing an entry”. See also the FAQ on “GitHub pull request” @@ -3104,15 +3107,15 @@ 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 +to a particular IOCCC entry, please see the FAQ on “report entry bug” -for information about reporting a bug in an IOCCC entry, and see +for information about reporting a bug in an IOCCC entry, and see the FAQ on “fixing 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 +the IOCCC website. See the FAQ on “fixing the website” for information on submitting fixes to the IOCCC website.

      @@ -3128,14 +3131,14 @@ to open a new IOCCC iss

      For IOCCC website problems that relate to a particular IOCCC entry, please -see +see the FAQ on “fixing an entry” for information on how submit a fix to an IOCCC entry.

      You may open a GitHub pull request against the master branch of the ioccc-src/winner repo to submit a fix.

      -

      Please see +

      Please see the FAQ on “fixing an entry”. See also the FAQ on “GitHub pull request” @@ -3163,7 +3166,7 @@ AND then run make www from the top level directory in your IOCCC pu 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 +

      Please see the FAQ on “fixing an entry”.

      See also the FAQ on “GitHub pull request” diff --git a/faq.md b/faq.md index 8377ed438..0ced54a46 100644 --- a/faq.md +++ b/faq.md @@ -203,7 +203,7 @@ where: * remarks.md - Remarks about your entry in markdown format: see + Remarks about your entry in markdown format: see the FAQ on "[remarks.md](#remarks_md)" for more info. @@ -260,7 +260,7 @@ 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 +of your `remarks.md` file, see the 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** @@ -361,7 +361,7 @@ state something along the lines of: ``` **FAIR WARNING**: Be sure to **clearly explain** near the beginning -of your `remarks.md` file, see +of your `remarks.md` file, see the 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** @@ -527,7 +527,7 @@ 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 +See also the FAQ on "[rules, guidelines, tools feedback](#feedback)". @@ -622,7 +622,7 @@ submission: - `mastodon` (null or double quoted string) * The Mastodon handle of this author in the form of `@user@domain`, or - `null` if not provided. See + `null` if not provided. See the FAQ on "[Mastodon](#try_mastodon)" for more information. @@ -658,9 +658,9 @@ 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 + See the FAQ on "[author handle](#author_handle_faq)" - and + and the FAQ on "[author_handle.json](#author_json)" for more information. @@ -794,7 +794,7 @@ The file also contains the following details: - `formed_timestamp` (number) * Seconds since epoch when `.auth.json was formed (see `gettimeofday(2)`). - See also + See also the FAQ on "[.info.json](#info_json)" for more inforation. @@ -871,7 +871,7 @@ the **mandatory** `remarks.md` file, and the **mandatory** C source file. See the FAQ on "[.auth.json](#auth_json)" -and +and the FAQ on "[remarks.md](#remarks_md)" for more inforation. @@ -1931,7 +1931,7 @@ 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 +the spirit of the original code are very welcome! Please see the FAQ on "[fixing an entry](#fix_an_entry)" for details. See also the FAQ on "[GitHub pull request](#pull_request)" @@ -1953,7 +1953,7 @@ 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 +Please see the FAQ on "[fixing an entry](#fix_an_entry)" for details. @@ -1979,7 +1979,7 @@ 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 +form of a pull request. Please see the FAQ on "[fixing an entry](#fix_an_entry)". See also the FAQ on "[GitHub pull request](#pull_request)" @@ -2091,7 +2091,7 @@ the [thanks-for-help.html](thanks-for-help.html) file. #### Red Hat based Linux -First, see +First, see the FAQ on "[general X11](#X11_general)". Install Xorg and related packages: @@ -2658,7 +2658,7 @@ 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 +Please see the FAQ on "[fixing an entry](#fix_an_entry)" for how to submit a fix to an IOCCC entry. @@ -2939,7 +2939,7 @@ 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 +In general OpenGL needs X11 to be installed and the X Window Server to be running. See the FAQ on "[X11](#X11)" for general information about X11. @@ -3376,7 +3376,7 @@ 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 +See also the FAQ on "[entry source code changes](#what_changed)" @@ -3461,11 +3461,15 @@ 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 on "[try.sh and try.alt.sh](#try)", +`try.sh` sometimes the `try.alt.sh` scripts 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). +See the +FAQ on "[try.sh and try.alt.sh](#try)" +for more details. + Alternate code, sometimes provided by the author, sometimes provided by the judges and sometimes other people, was added to some entries as well. @@ -3497,7 +3501,7 @@ 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 +See the 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, @@ -3530,7 +3534,7 @@ 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 +Please see the FAQ on "[fixing an entry](#fix_an_entry)" for information on how to submit a fix to an IOCCC entry. See also the @@ -3577,7 +3581,7 @@ 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 +Please see the FAQ on "[fixing an entry](#fix_an_entry)". See also the FAQ on "[GitHub pull request](#pull_request)" @@ -3594,16 +3598,16 @@ 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 +to a particular IOCCC entry, please see the FAQ on "[report entry bug](#report_bug)" -for information about reporting a bug in an IOCCC entry, and see +for information about reporting a bug in an IOCCC entry, and see the 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 +the IOCCC website. See the FAQ on "[fixing the website](#fix_web_site)" for information on submitting fixes to the IOCCC website. @@ -3623,7 +3627,7 @@ 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 +see the FAQ on "[fixing an entry](#fix_an_entry)" for information on how submit a fix to an IOCCC entry. @@ -3632,7 +3636,7 @@ 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 +Please see the FAQ on "[fixing an entry](#fix_an_entry)". See also the FAQ on "[GitHub pull request](#pull_request)" @@ -3672,7 +3676,7 @@ 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 +Please see the FAQ on "[fixing an entry](#fix_an_entry)". See also the diff --git a/index.html b/index.html index f9891b69b..95a9e8294 100644 --- a/index.html +++ b/index.html @@ -435,7 +435,7 @@ FAQ on “website menus”.

    Entering the Contest

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

    -

    See +

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

    Important Disclaimer

    diff --git a/index.md b/index.md index 17aea2a64..b6cfb3ab3 100644 --- a/index.md +++ b/index.md @@ -65,7 +65,7 @@ The goals of the IOCCC: View the [current status of the IOCCC](status.html) to see of the IOCCC is open for submissions. -See +See the FAQ on "[how to submit](faq.html#submit)" for more information. diff --git a/news.html b/news.html index b93eab6a2..984cfe670 100644 --- a/news.html +++ b/news.html @@ -392,7 +392,7 @@

    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 +

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

    News

    diff --git a/news.md b/news.md index 478452777..1c5061553 100644 --- a/news.md +++ b/news.md @@ -5,7 +5,7 @@ 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 +See the FAQ on "[Mastodon](faq.html#try_mastodon)" for more information on Mastodon. diff --git a/next/guidelines.html b/next/guidelines.html index 7799c46ba..561bb50fd 100644 --- a/next/guidelines.html +++ b/next/guidelines.html @@ -477,7 +477,7 @@ 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 +website on or slightly before start of this IOCCC. Please check our 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 @@ -942,7 +942,7 @@ 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 +bug_report.sh script to help us out here! See the FAQ on “report mkiocccentry bugs”.

    @@ -957,7 +957,7 @@ 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 +See the FAQ on “report mkiocccentry bugs”.

    @@ -1047,7 +1047,7 @@ 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 +while you may wish to try it, you should read our FAQ on “clang -Weverything”. We do NOT recommend that you put the use of -Weverything into your submission’s Makefile for the reasons @@ -1887,7 +1887,7 @@ It has been shown that receiving anonymous gifts provides the IOCCC judges help make the IOCCC better for everyone. :-)

    -See +See the FAQ on “support the IOCCC”.

    More often than not, we select a small submission (usually one line) and a diff --git a/next/guidelines.md b/next/guidelines.md index 0f3c5282d..33e505f2f 100644 --- a/next/guidelines.md +++ b/next/guidelines.md @@ -116,7 +116,7 @@ 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 +website](https://www.ioccc.org) on or slightly before start of this IOCCC. Please check our 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 @@ -356,7 +356,7 @@ 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 +**PLEASE run the `bug_report.sh` script to help us out here!** See the FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".

    @@ -615,7 +615,7 @@ 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 +`bug_report.sh` script to help us out here!** See the FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".

    @@ -632,7 +632,7 @@ 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 +See the FAQ on "[report mkiocccentry bugs](../faq.html#mkiocccentry_bugs)".

    @@ -755,7 +755,7 @@ 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 +while you may wish to try it, you should read our 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 @@ -1771,7 +1771,7 @@ It has been shown that receiving **anonymous** gifts provides the

    -See +See the FAQ on "[support the IOCCC](../faq.html#support)".

    diff --git a/next/rules.html b/next/rules.html index 6180ebe9c..2e77232d8 100644 --- a/next/rules.html +++ b/next/rules.html @@ -474,7 +474,7 @@ 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 +

    Please review our FAQ on “how to submit” for important information on how to submit to the IOCCC.

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

    Rule 3

    -

    Submissions should be performed using the instructions outlined at: -the +

    Submissions should be performed using the instructions outlined in our 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 @@ -700,7 +699,7 @@ 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 +See the FAQ on “how to register” for details.

    @@ -839,7 +838,7 @@ for help. The remarks.md MUST be a non-empty file in markdown form. See also Rule 18 and our FAQ on “remarks.md” -and the +and our FAQ on “markdown practices”.

    @@ -966,7 +965,7 @@ 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 +for help here and also read our FAQ on “mkiocccentry repo bugs”.

    diff --git a/next/rules.md b/next/rules.md index b95faeb67..630aed2c6 100644 --- a/next/rules.md +++ b/next/rules.md @@ -114,7 +114,7 @@ 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 +Please review our FAQ on "[how to submit](../faq.html#submit)" for **important information** on how to submit to the IOCCC. @@ -251,8 +251,7 @@ as a command like argument to the `iocccsize(1)` tool. For example: ## Rule 3 -Submissions should be performed using the instructions outlined at: -the +Submissions should be performed using the instructions outlined in our FAQ on "[how to submit](../faq.html#submit)" To submit to an open IOCCC, you must use the [IOCCC submit @@ -433,7 +432,7 @@ enough time for one automated exchange of email as part of your submission.

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

    @@ -570,7 +569,7 @@ for help. The `remarks.md` **MUST** be a **non**-empty file in markdown form. See also [Rule 18](#rule18) and our FAQ on "[remarks.md](../faq.html#remarks_md)" -and the +and our FAQ on "[markdown practices](../faq.html#markdown)".

    @@ -699,7 +698,7 @@ 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 +for help here and also read our FAQ on "[mkiocccentry repo bugs](../faq.html#mkiocccentry_bugs)".

    diff --git a/thanks-for-help.html b/thanks-for-help.html index 2915ac897..bbef46865 100644 --- a/thanks-for-help.html +++ b/thanks-for-help.html @@ -549,7 +549,8 @@ 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 +needed and is unused) has been added just in case.

    +

    See the FAQ on “main function args” for more details.

    Cody also added the script primes.sh which allows one @@ -682,11 +683,12 @@ 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 on “gets and fgets” -for why this was done. +

    Cody made this use fgets(). Cody also added the try.sh script which also feeds to the program the input.txt text file that Cody added.

    +

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

    Winning entry: 1986/holloway

    Winning entry source code: holloway.c

    @@ -894,7 +896,8 @@ size constraints of the contest).

    Winning entry: 1987/wall

    Winning entry source code: wall.c

    -

    Cody made this use fgets(3). See +

    Cody made this use fgets(3).

    +

    See the FAQ on “gets and fgets” for why this was done.

    Cody also added the try.sh script.

    @@ -1009,7 +1012,8 @@ 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 +

    Cody made this use fgets(3).

    +

    See the FAQ on “gets and fgets” for why this was done.

    @@ -1270,7 +1274,8 @@ 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 +

    Cody made this use fgets(3).

    +

    See the FAQ on “gets and fgets” for why this was done.

    @@ -1285,7 +1290,8 @@ 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 +

    Cody also made this use fgets(3).

    +

    See the FAQ on “gets and fgets” for why this was done.

    @@ -1347,7 +1353,8 @@ 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 +warning being interspersed with the program’s interactive output.

    +

    See the FAQ on “gets and fgets” for more details on why this change was done more generally.

    @@ -1370,7 +1377,8 @@ 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 +

    Cody also changed the code to use fgets(3).

    +

    See the FAQ on “gets and fgets” for why this was done.

    Since this program is so incredible the extra fixes were deemed worth having and @@ -1481,7 +1489,8 @@ 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 +gets().

    +

    See the FAQ on “gets and fgets” for why this was done.

    For the magic of clang (which was done manually except the returning a value @@ -1642,11 +1651,11 @@ true of another change as further below.

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

    Cody also changed the location that it used gets() to be fgets(3).

    +

    See the FAQ on “gets and fgets” -for why this was done. -This was complicated because of how the other source files are generated (as +for general information about to 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).

    One might think that simply changing the gets(3) to fgets(3) (with stdin) @@ -1770,7 +1779,8 @@ 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 +changing this.

    +

    See the FAQ on “main function args” for more details.

    Yusuke also noted that there is a bug in the program where right after starting @@ -1785,7 +1795,8 @@ 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 +

    Cody made it use fgets() instead of gets().

    +

    See the FAQ on “gets and fgets” for why this was done.

    NOTE: this entry cannot work with clang due to different compiler messages (it @@ -1959,7 +1970,8 @@ 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 +

    Cody made this use fgets(3) not gets(3).

    +

    See the FAQ on “gets and fgets” for why this was done.

    @@ -2049,10 +2061,10 @@ comma operator was needed.

    Cody also fixed it for clang under Linux which objected to incompatible pointer 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 +

    Cody also changed the entry to use fgets(3) instead of gets(3).

    +

    See the FAQ on “gets and fgets” -for why this was done.)

    +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 @@ -2112,15 +2124,15 @@ remarks), try.alt.bw.sh, respectively. The scripts go through 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 on “gets and fgets” -]for why this was done. -In this case the newline had +

    Cody also made this use fgets(3) instead of gets(3).

    +

    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 more like the original entry this was done in the Makefile. The alternate code was also changed to use fgets(3).

    +

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

    Winning entry: 1994/weisberg

    Winning entry source code: weisberg.c

    @@ -2164,7 +2176,8 @@ 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 +function as the error message claims.

    +

    See the FAQ on “main function args” for more details.

    @@ -2381,7 +2394,8 @@ 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 +be a problem at such a time.

    +

    See the FAQ on “main function args” for more details.

    Cody also added the bas1.sh script to simplify running the @@ -2451,7 +2465,8 @@ 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 +code look like the original with just an extra arg.

    +

    See the FAQ on “main function args” for more details.

    In some versions of clang -Wno-int-conversion had to be added to the @@ -2550,7 +2565,8 @@ 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 +from breaking if that happens.

    +

    See the FAQ on “main function args” for more details.

    Cody added the try.sh script to make it easier to try @@ -2589,11 +2605,11 @@ commands that we recommended.

    Winning entry source code: anderson.c

    Cody changed this entry to use fgets(3) instead of gets(3). -See +This involved changing the K arg to gets(3) to &K in fgets(3). +Cody also added the try.sh script.

    +

    See the 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.

    +for why this was done.

    Winning entry: 2000/bmeyer

    Winning entry source code: bmeyer.c

    @@ -3082,7 +3098,8 @@ 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 +is entirely possible it will eventually be that they don’t.

    +

    See the FAQ on “main function args” for more details.

    Cody also added the try.sh script and various data @@ -3107,7 +3124,8 @@ chose the word IOCCC instead of AAA).

    Winning entry: 2004/schnitzi

    Winning entry source code: schnitzi.c

    -

    Cody made this use fgets(3). See +

    Cody made this use fgets(3).

    +

    See the 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 @@ -3472,7 +3490,8 @@ 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 +args, even though at least one of those versions allows 1 arg only.

    +

    See the FAQ on “main function args” for more details.

    Cody also added the try.sh script for easier use of the @@ -3530,7 +3549,8 @@ 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 +the number of args as well.

    +

    See the FAQ on “main function args” for more details.

    Cody also added the try.sh script.

    @@ -3702,7 +3722,8 @@ 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 +restrict them.

    +

    See the FAQ on “main function args” for more details.

    Cody also restored the original code from the archive.

    @@ -3917,7 +3938,8 @@ also appear to be an issue with the script even if you know of convert

    Cody 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 +arg type and count to main()) added a second (unused) arg to main().

    +

    See the FAQ on “main function args” for more details.

    @@ -4272,7 +4294,8 @@ 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 +(that’s not needed and is unused) has been added just in case.

    +

    See the FAQ on “main function args” for more details.

    Cody also added explicit linking of libm (-lm) for systems that do not do this diff --git a/thanks-for-help.md b/thanks-for-help.md index 12a942e18..1a447764b 100644 --- a/thanks-for-help.md +++ b/thanks-for-help.md @@ -217,7 +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 +needed and is unused) has been added just in case. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -403,12 +405,14 @@ 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 on "[gets and fgets](faq.html#gets)" -for why this was done. +[Cody](#cody) made this use `fgets()`. 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. +See the +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. +
    ## Winning entry: [1986/holloway](1986/holloway/index.html) @@ -723,7 +727,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 +[Cody](#cody) made this use `fgets(3)`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. @@ -889,12 +895,13 @@ 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 +[Cody](#cody) made this use `fgets(3)`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. -
    ## Winning entry: [1988/spinellis](1988/spinellis/index.html) ### Winning entry source code: [spinellis.c](%%REPO_URL%%/1988/spinellis/spinellis.c) @@ -1246,7 +1253,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 +[Cody](#cody) made this use `fgets(3)`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. @@ -1269,7 +1278,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 +Cody also made this use `fgets(3)`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. @@ -1360,7 +1371,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 +warning being interspersed with the program's interactive output. + +See the FAQ on "[gets and fgets](faq.html#gets)" for more details on why this change was done more generally. @@ -1393,7 +1406,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 +Cody also changed the code to use `fgets(3)`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. @@ -1544,7 +1559,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 +`gets()`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. @@ -1798,9 +1815,11 @@ 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 + +See the FAQ on "[gets and fgets](faq.html#gets)" -for why this was done. +for general information about to 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). @@ -1969,7 +1988,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 +changing this. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -1991,7 +2012,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 +Cody made it use `fgets()` instead of `gets()`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. @@ -2231,7 +2254,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 +[Cody](#cody) made this use `fgets(3)` not `gets(3)`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. @@ -2358,9 +2383,10 @@ 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 + +See the FAQ on "[gets and fgets](faq.html#gets)" -for why this was done.) +for why this was done. This one has a minor annoyance in that it now prints a newline after the output but this @@ -2439,15 +2465,17 @@ 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 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 more like the original entry this was done in the Makefile. The alternate code was also changed to use `fgets(3)`. +See the +FAQ on "[gets and fgets](faq.html#gets)" +for why this was done. +
    ## Winning entry: [1994/weisberg](1994/weisberg/index.html) @@ -2505,12 +2533,13 @@ 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 +function as the error message claims. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. -
    ## Winning entry: [1995/dodsond1](1995/dodsond1/index.html) ### Winning entry source code: [dodsond1.c](%%REPO_URL%%/1995/dodsond1/dodsond1.c) @@ -2807,7 +2836,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 +be a problem at such a time. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -2905,7 +2936,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 +code look like the original with just an extra arg. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -3045,7 +3078,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 +from breaking if that happens. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -3103,12 +3138,12 @@ commands that we recommended.
    [Cody](#cody) changed this entry to use `fgets(3)` instead of `gets(3)`. -See +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. + +See the 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.
    @@ -3797,7 +3832,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 +is entirely possible it will eventually be that they don't. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -3833,7 +3870,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 +[Cody](#cody) made this use `fgets(3)`. + +See the FAQ on "[gets and fgets](faq.html#gets)" for why this was done. @@ -4353,7 +4392,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 +args, even though at least one of those versions allows 1 arg only. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -4437,7 +4478,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 +the number of args as well. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -4678,7 +4721,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 +restrict them. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. @@ -4972,13 +5017,13 @@ The entry can still be enjoyed if you do not have these tools, however. [Cody](#cody) added the [try.sh](%%REPO_URL%%/2013/endoh3/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 +arg type and count to `main()`) added a second (unused) arg to `main()`. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details. - -
    ## Winning entry: [2013/endoh4](2013/endoh4/index.html) ### Winning entry source code: [endoh4.c](%%REPO_URL%%/2013/endoh4//endoh4.c) @@ -5488,7 +5533,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 +(that's not needed and is unused) has been added just in case. + +See the FAQ on "[main function args](faq.html#arg_count)" for more details.