improve word flow around FAQ references
This commit is contained in:
Landon Curt Noll committed
1 parent
f7e7610370
commit
89e66b96c5
41 files changed
+289
-213
No files matched your search
@@ -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.
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -417,7 +417,7 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
|
||||
<p>NOTE: if you don’t have curses or SDL1 installed both modes will fail to compile. In
|
||||
that case see the
|
||||
FAQ on “<a href="../../faq.html#SDL">SDL1 and SDL2</a>”
|
||||
and
|
||||
and the
|
||||
FAQ on “<a href="../../faq.html#curses">ncurses</a>”
|
||||
for more information.</p>
|
||||
<p>We recommend that you use the alternate code so you can see what this entry
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -412,7 +412,7 @@ Location: <a href="../../location.html#FR">FR</a> - <em>French Republic</em> (<e
|
||||
<h2 id="to-use">To use:</h2>
|
||||
<p>You will need an <a href="https://www.w3.org/TR/SVG11/expanded-toc.html">SVG</a> viewer or
|
||||
a converter like <a href="https://imagemagick.org/index.php">ImageMagick</a>’s <code>convert</code>.
|
||||
See
|
||||
See the
|
||||
FAQ on “<a href="../../faq.html#imagemagick">ImageMagick</a>”.</p>
|
||||
<p>Look here to find some <a href="https://www.w3.org/Graphics/SVG/WG/wiki/Implementations">SVG Viewer
|
||||
Implementations</a>.</p>
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -408,7 +408,7 @@ Location: <a href="../../location.html#FI">FI</a> - <em>Republic of Finland </em
|
||||
|
||||
<!-- BEFORE: 1st line of markdown file: 2005/jetro/README.md -->
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<p>This entry requires SDL. See
|
||||
<p>This entry requires SDL. See the
|
||||
FAQ on “<a href="../../faq.html#SDL">SDL1 and SDL2</a>”
|
||||
for information on how to install it if you
|
||||
haven’t already.</p>
|
||||
|
||||
@@ -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)".
|
||||
|
||||
|
||||
|
||||
@@ -437,8 +437,8 @@ minutes</a>
|
||||
just to understand <em>18 key <strong>characters</strong></em> of this code.</p>
|
||||
<p>NOTE: if you use vim to view the code, make sure to do:</p>
|
||||
<pre><code> :set tabstop=4</code></pre>
|
||||
<p>in command mode, before looking at the code, to see the correct layout. For more
|
||||
help see the
|
||||
<p>in command mode, before looking at the code, to see the correct layout.</p>
|
||||
<p>For more help, see the
|
||||
FAQ on “<a href="../../faq.html#tabstops">tabstops</a>”.</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<h3 id="nesting-errors-detector">Nesting Errors Detector</h3>
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -417,7 +417,7 @@ Location: <a href="../../location.html#JP">JP</a> - <em>Japan</em></li>
|
||||
<p>For more detailed information see <a href="../../bugs.html#2013_endoh3">2013/endoh3 in bugs.html</a>.</p>
|
||||
<h2 id="to-use">To use:</h2>
|
||||
<pre><code> ./endoh3</code></pre>
|
||||
<p>This program plays sound. See
|
||||
<p>This program plays sound. See the
|
||||
FAQ on “<a href="../../faq.html#sox">compile with sound</a>”
|
||||
if you do not know how to set your
|
||||
system up for this or if you want to verify that everything is oky.</p>
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -408,7 +408,7 @@ Location: <a href="../../location.html#IT">IT</a> - <em>Italian Republic</em> (<
|
||||
|
||||
<!-- BEFORE: 1st line of markdown file: 2014/maffiodo1/README.md -->
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<p>This entry requires SDL to be installed. See
|
||||
<p>This entry requires SDL to be installed. See the
|
||||
FAQ on “<a href="../../faq.html#SDL">SDL1 and SDL2</a>”
|
||||
if you don’t know how to do this for your system.</p>
|
||||
<pre><code> make</code></pre>
|
||||
|
||||
@@ -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)".
|
||||
|
||||
|
||||
|
||||
@@ -415,7 +415,7 @@ Location: <a href="../../location.html#JP">JP</a> - <em>Japan</em></li>
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<pre><code> make</code></pre>
|
||||
<p>NOTE: this program requires the tool <code>tcpserver</code> to use. If you do not have this
|
||||
program see
|
||||
program see the
|
||||
FAQ on “<a href="../../faq.html#tcpserver">tcpserver</a>”.</p>
|
||||
<h2 id="to-use">To use:</h2>
|
||||
<pre><code> tcpserver -v 127.0.0.1 10333 ./prog ioccc.txt</code></pre>
|
||||
|
||||
@@ -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)".
|
||||
|
||||
|
||||
|
||||
@@ -410,7 +410,7 @@ Location: <a href="../../location.html#SE">SE</a> - <em>Kingdom of Sweden</em> (
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<pre><code> make</code></pre>
|
||||
<p>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 “<a href="../../faq.html#sox">SDL1 and SDL2</a>”.</p>
|
||||
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
|
||||
<p>The current status of this entry is:</p>
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -420,9 +420,9 @@ graphics viewer of choice. After that try:</p>
|
||||
<pre><code> ./try.sh</code></pre>
|
||||
<p>NOTE: the script uses the tools <code>pngtopam(1)</code> (or <code>pngtopnm(1)</code> for older
|
||||
versions) and <code>pnmscale</code> come from the netpbm project and <code>cjpeg(1)</code> comes from
|
||||
<code>libjpeg-turbo</code>. If you don’t have these tools already see
|
||||
<code>libjpeg-turbo</code>. If you don’t have these tools already see the
|
||||
FAQ on “<a href="../../faq.html#netpbm">netpbm</a>”
|
||||
and
|
||||
and the
|
||||
FAQ on “<a href="../../faq.html#libjpeg">libjpeg-turbo</a>”.</p>
|
||||
<p>NOTE: <a href="Lenna.png">Lenna.png</a> is from
|
||||
<a href="https://upload.wikimedia.org/wikipedia/en/7/7d/Lenna_%28test_image%29.png" class="uri">https://upload.wikimedia.org/wikipedia/en/7/7d/Lenna_%28test_image%29.png</a>.</p>
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -408,7 +408,7 @@ Location: <a href="../../location.html#AU">AU</a> - <em>Commonwealth of Australi
|
||||
|
||||
<!-- BEFORE: 1st line of markdown file: 2018/giles/README.md -->
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<p>This entry requires SDL2 to be installed. See
|
||||
<p>This entry requires SDL2 to be installed. See the
|
||||
FAQ on “<a href="../../faq.html#SDL">SDL1 and SDL2</a>”
|
||||
if you don’t have it
|
||||
installed and don’t know how to do so.</p>
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -454,7 +454,7 @@ better with it.</p>
|
||||
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.</p>
|
||||
<p>Special note for Mac users: <code>Terminal.app</code> does not work as expected; you might
|
||||
need xterm from XQuartz, see
|
||||
need xterm from XQuartz, see the
|
||||
FAQ on “<a href="../../faq.html#X11macos">X11 on macOS</a>”,
|
||||
or some other working
|
||||
terminal. Thanks to <a href="../../authors.html#Dave_Burton">Dave Burton</a> for spotting this
|
||||
|
||||
@@ -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)".
|
||||
|
||||
|
||||
|
||||
@@ -414,7 +414,7 @@ Location: <a href="../../location.html#AU">AU</a> - <em>Commonwealth of Australi
|
||||
<h2 id="try">Try:</h2>
|
||||
<pre><code> ./try.sh</code></pre>
|
||||
<p>NOTE: <code>play</code>, which <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/giles/try.sh">try.sh</a> 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 “<a href="../../faq.html#sox">SDL1 and SDL2</a>”.</p>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>Do you need to pretend enjoying a more spacious living environment than you
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -431,7 +431,7 @@ will be converted to the DTMF sound!</p>
|
||||
# See
|
||||
./prog 867-5309 > jenny.wav</code></pre>
|
||||
<p>If the script <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/giles/try.sh">try.sh</a> did not play a WAV file, it means you do not have
|
||||
SoX installed; see
|
||||
SoX installed; see the
|
||||
FAQ on “<a href="../../faq.html#sox">SDL1 and SDL2</a>”.
|
||||
In this case install it and try it again or
|
||||
play the files <code>jenny.wav</code> and <code>ioccc28.wav</code> in a program that can play WAV
|
||||
|
||||
+11
-11
@@ -391,13 +391,13 @@
|
||||
<h1 id="wait---before-you-send-that-email">WAIT!!! - Before you send that email</h1>
|
||||
<p>If you are trying to:</p>
|
||||
<ul>
|
||||
<li><strong>Fix a winning IOCCC entry</strong> - See
|
||||
<li><strong>Fix a winning IOCCC entry</strong> - See our
|
||||
FAQ on “<a href="faq.html#fix_an_entry">fix entry</a>”</li>
|
||||
<li><strong>Update winning author information</strong> - See
|
||||
<li><strong>Update winning author information</strong> - See our
|
||||
FAQ on “<a href="faq.html#fix_author">fixing author information</a>”</li>
|
||||
<li><strong>Correct a website problem</strong> - See
|
||||
<li><strong>Correct a website problem</strong> - See our
|
||||
FAQ on “<a href="faq.html#fix_web_site">fixing the website</a>”
|
||||
or
|
||||
or our
|
||||
FAQ on “<a href="faq.html#fix_link">fix URL</a>”</li>
|
||||
</ul>
|
||||
<p>Instead of sending us email, <strong>Please</strong> consider using the <a href="https://github.com/ioccc-src/winner/pulls">GitHub
|
||||
@@ -406,11 +406,11 @@ against the <a href="https://github.com/ioccc-src/winner/branches">master branch
|
||||
of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner repo</a>.</p>
|
||||
<p>If you are trying to:</p>
|
||||
<ul>
|
||||
<li><strong>Report a bug in an IOCCC winning entry</strong> - See
|
||||
<li><strong>Report a bug in an IOCCC winning entry</strong> - See our
|
||||
FAQ on “<a href="faq.html#report_bug">report entry bug</a>”</li>
|
||||
<li><strong>Report an IOCCC website problem</strong> - See
|
||||
<li><strong>Report an IOCCC website problem</strong> - See our
|
||||
FAQ on “<a href="faq.html#report_web_problem">report website problem</a>”</li>
|
||||
<li><strong>Report a broken or wrong web link</strong> - See
|
||||
<li><strong>Report a broken or wrong web link</strong> - See our
|
||||
FAQ on “<a href="faq.html#fix_link">report broken link</a>”</li>
|
||||
</ul>
|
||||
<p>In general, unless you have a fix, if you want to report something, you should instead first look at the <a href="https://github.com/ioccc-src/winner/issues">IOCCC
|
||||
@@ -421,11 +421,11 @@ reported, then feel free to <a href="https://github.com/ioccc-src/winner/issues/
|
||||
issue</a>.</p>
|
||||
<p>If you are trying to:</p>
|
||||
<ul>
|
||||
<li><strong>Comment or make a suggestion on IOCCC rules</strong> - See
|
||||
<li><strong>Comment or make a suggestion on IOCCC rules</strong> - See our
|
||||
FAQ on “<a href="faq.html#feedback">rules feedback</a>”</li>
|
||||
<li><strong>Comment or make a suggestion on IOCCC guidelines</strong> - See
|
||||
<li><strong>Comment or make a suggestion on IOCCC guidelines</strong> - See our
|
||||
FAQ on “<a href="faq.html#feedback">guidelines feedback</a>”</li>
|
||||
<li><strong>Comment or make a suggestion on IOCCC tools</strong> - See
|
||||
<li><strong>Comment or make a suggestion on IOCCC tools</strong> - See our
|
||||
FAQ on “<a href="faq.html#feedback">tools feedback</a>”</li>
|
||||
</ul>
|
||||
<p>Those FAQ entries will help guide you on how to make public comments
|
||||
@@ -437,7 +437,7 @@ and suggestion in the relevant places.</p>
|
||||
<h2 id="please-follow-the-ioccc-on-mastodon">Please follow the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h2>
|
||||
<p>We use Mastodon to make minor announcements, in addition announcing
|
||||
major events such as the opening of a new IOCCC, or who won.</p>
|
||||
<p>See
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#try_mastodon">Mastodon</a>”
|
||||
for more information on Mastodon.</p>
|
||||
<h1 id="if-you-really-need-to-send-email-the-ioccc-judges">If you really need to send email the IOCCC judges</h1>
|
||||
|
||||
+11
-11
@@ -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.
|
||||
|
||||
|
||||
@@ -545,7 +545,7 @@ to our submission portal.</p>
|
||||
<li><p>Makefile</p>
|
||||
<p>Makefile to build (make all) and cleanup (make clean & make clobber)</p></li>
|
||||
<li><p>remarks.md</p>
|
||||
<p>Remarks about your entry in markdown format: see
|
||||
<p>Remarks about your entry in markdown format: see the
|
||||
FAQ on “<a href="#remarks_md">remarks.md</a>”
|
||||
for more info.</p></li>
|
||||
<li><p>[file …]</p>
|
||||
@@ -585,7 +585,7 @@ winners based on the same theme.</p>
|
||||
frequently submitted theme, be sure that it is obfuscated in several
|
||||
new and novel ways.</p>
|
||||
<p><strong>IMPORTANT HINT</strong>: Be sure to <strong>clearly explain</strong> near the beginning
|
||||
of your <code>remarks.md</code> file, see
|
||||
of your <code>remarks.md</code> file, see the
|
||||
FAQ on “<a href="#remarks_md">remarks.md</a>”,
|
||||
<strong>why you are submitting a entry based on a frequently
|
||||
submitted theme</strong> and <strong>how compares with previous IOCCC winners</strong>
|
||||
@@ -665,7 +665,7 @@ previous IOCCC entries make it more challenging to be successful.</p>
|
||||
state something along the lines of:</p>
|
||||
<pre><code> We tend to dislike programs that: are similar to previous winning entries.</code></pre>
|
||||
<p><strong>FAIR WARNING</strong>: Be sure to <strong>clearly explain</strong> near the beginning
|
||||
of your <code>remarks.md</code> file, see
|
||||
of your <code>remarks.md</code> file, see the
|
||||
FAQ on “<a href="#remarks_md">remarks.md</a>”,
|
||||
<strong>why you are submitting a entry based on a frequently
|
||||
submitted theme</strong> and <strong>how compares with previous IOCCC winners</strong>
|
||||
@@ -792,7 +792,7 @@ with your submission. If the <a href="judges.html">IOCCC judges</a> truly need m
|
||||
information, they will ask (either in public or suggest a private conversation).</p>
|
||||
<p>Again, <strong>please</strong> don’t hesitate to ask: Your question may be something that
|
||||
others are wondering about as well!</p>
|
||||
<p>See also
|
||||
<p>See also the
|
||||
FAQ on “<a href="#feedback">rules, guidelines, tools feedback</a>”.</p>
|
||||
<div id="faq0_7">
|
||||
<div id="markdown">
|
||||
@@ -874,7 +874,7 @@ for a list of valid codes.</li>
|
||||
<li><p><code>mastodon</code> (null or double quoted string)</p>
|
||||
<ul>
|
||||
<li>The Mastodon handle of this author in the form of <code>@user@domain</code>, or
|
||||
<code>null</code> if not provided. See
|
||||
<code>null</code> if not provided. See the
|
||||
FAQ on “<a href="#try_mastodon">Mastodon</a>”
|
||||
for more information.</li>
|
||||
</ul></li>
|
||||
@@ -912,9 +912,9 @@ by this author.</li>
|
||||
<p><strong>NOTE:</strong> if you have won before, we <strong>ENCOURAGE</strong> you to use the same handle of
|
||||
your previous winning entries, to help in organising the
|
||||
<a href="authors.html">authors.html</a> page and the author JSON file.
|
||||
See
|
||||
See the
|
||||
FAQ on “<a href="#author_handle_faq">author handle</a>”
|
||||
and
|
||||
and the
|
||||
FAQ on “<a href="#author_json">author_handle.json</a>”
|
||||
for more information.</p></li>
|
||||
<li><p><code>author_number</code> (number)</p>
|
||||
@@ -1047,7 +1047,7 @@ array your submission <strong>will be</strong> invalid.</p></li>
|
||||
<li><p><code>formed_timestamp</code> (number)</p>
|
||||
<ul>
|
||||
<li>Seconds since epoch when <code>.auth.json was formed (see</code>gettimeofday(2)`).
|
||||
See also
|
||||
See also the
|
||||
FAQ on “<a href="#info_json">.info.json</a>”
|
||||
for more inforation.</li>
|
||||
</ul>
|
||||
@@ -1118,7 +1118,7 @@ the <strong>mandatory</strong> <code>remarks.md</code> file,
|
||||
and the <strong>mandatory</strong> C source file.
|
||||
See the
|
||||
FAQ on “<a href="#auth_json">.auth.json</a>”
|
||||
and
|
||||
and the
|
||||
FAQ on “<a href="#remarks_md">remarks.md</a>”
|
||||
for more inforation.</p>
|
||||
<ul>
|
||||
@@ -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 “<a href="#fix_an_entry">fixing an entry</a>”
|
||||
for details. See also the
|
||||
FAQ on “<a href="#pull_request">GitHub pull request</a>”
|
||||
@@ -2048,7 +2048,7 @@ others will be looked at, when found.</p>
|
||||
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 “<a href="#fix_an_entry">fixing an entry</a>”
|
||||
for details.</p>
|
||||
<div id="faq3_4">
|
||||
@@ -2068,7 +2068,7 @@ other things that have to be done plus remembering to do it.</p>
|
||||
<p>See if the problem is mentioned in <a href="bugs.html">bugs.html</a>. If you have a change
|
||||
that fixes the problem (even if it just a change to the <code>Makefile</code>) 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 “<a href="#fix_an_entry">fixing an entry</a>”.
|
||||
See also the
|
||||
FAQ on “<a href="#pull_request">GitHub pull request</a>”
|
||||
@@ -2155,7 +2155,7 @@ for more information.</p>
|
||||
provide <strong>alternate code</strong> that works for Wayland. We will happily credit you in
|
||||
the <a href="thanks-for-help.html">thanks-for-help.html</a> file.</p>
|
||||
<h4 id="red-hat-based-linux">Red Hat based Linux</h4>
|
||||
<p>First, see
|
||||
<p>First, see the
|
||||
FAQ on “<a href="#X11_general">general X11</a>”.</p>
|
||||
<p>Install Xorg and related packages:</p>
|
||||
<pre><code> sudo dnf install --skip-broken --best --exclude xorgxrdp --exclude xorgxrdp-glamor '*xorg*' 'libx*' 'libX*' 'fontconfig*'</code></pre>
|
||||
@@ -2490,7 +2490,7 @@ that you may wish to try.</p>
|
||||
entry. If so, you are invited to try and fix the IOCCC entry and
|
||||
submit that fix by way of a <a href="https://github.com/ioccc-src/winner/pulls">GitHub pull
|
||||
request</a>.
|
||||
Please see
|
||||
Please see the
|
||||
FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
|
||||
for how to submit a fix to an IOCCC entry.</p>
|
||||
<div id="faq3_14">
|
||||
@@ -2629,7 +2629,7 @@ for downloading, installing and using ImageMagick.</p>
|
||||
</div>
|
||||
</div>
|
||||
<p>This depends on your operating system for which we describe a couple below.</p>
|
||||
<p>In general OpenGL needs X11 to be installed and the X Window Server to be running. See
|
||||
<p>In general OpenGL needs X11 to be installed and the X Window Server to be running. See the
|
||||
FAQ on “<a href="#X11">X11</a>”
|
||||
for general information about X11.</p>
|
||||
<p>Once X11 is install and the X Window Server is running, one needs to compile
|
||||
@@ -2939,7 +2939,7 @@ original code is in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/m
|
||||
some cases, such as <code>1984/mullender</code>, 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).</p>
|
||||
<p>See also
|
||||
<p>See also the
|
||||
FAQ on “<a href="#what_changed">entry source code changes</a>”</p>
|
||||
<div id="faq4_4">
|
||||
<h3 id="faq-4.4-what-is-the-meaning-of-the-file-ending-in-.orig.c-in-ioccc-entries">FAQ 4.4: What is the meaning of the file ending in .orig.c in IOCCC entries?</h3>
|
||||
@@ -3003,10 +3003,13 @@ other times something else.</p>
|
||||
<p>Like with files being renamed, there are multiple reasons files were added or
|
||||
removed. The addition of the <code>try.sh</code> and <code>try.alt.sh</code> scripts is the most
|
||||
significant example of files being added. These scripts, as the
|
||||
FAQ on “<a href="#try">try.sh and try.alt.sh</a>”,
|
||||
<code>try.sh</code> sometimes the <code>try.alt.sh</code> 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).</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="#try">try.sh and try.alt.sh</a>”
|
||||
for more details.</p>
|
||||
<p>Alternate code, sometimes provided by the author, sometimes provided by the
|
||||
judges and sometimes other people, was added to some entries as well.</p>
|
||||
<p>In the case that a link might end up with a 404 the files, if possible, were
|
||||
@@ -3028,7 +3031,7 @@ ways.</p>
|
||||
<p>The <a href="bugs.html">known bugs</a> 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.</p>
|
||||
<p>See
|
||||
<p>See the
|
||||
FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
|
||||
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
|
||||
<a href="thanks-for-help.html">thanks</a> 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.</p>
|
||||
<p>Please see
|
||||
<p>Please see the
|
||||
FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
|
||||
for information on how to submit a fix to an
|
||||
IOCCC entry. See also the
|
||||
@@ -3091,7 +3094,7 @@ IOCCC winning entries are presented!</p>
|
||||
<a href="https://github.com/ioccc-src/winner/pulls">GitHub pull request</a>
|
||||
against the <a href="https://github.com/ioccc-src/winner/branches">master branch</a>
|
||||
of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner repo</a>.</p>
|
||||
<p>Please see
|
||||
<p>Please see the
|
||||
FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.
|
||||
See also the
|
||||
FAQ on “<a href="#pull_request">GitHub pull request</a>”
|
||||
@@ -3104,15 +3107,15 @@ have the final say in the matter.</p>
|
||||
</div>
|
||||
</div>
|
||||
<p>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 “<a href="#report_bug">report entry bug</a>”
|
||||
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 “<a href="#fix_an_entry">fixing an entry</a>”
|
||||
for information on how to submit a fix to an IOCCC entry.</p>
|
||||
<p>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 <strong>not related
|
||||
to a particular IOCCC entry</strong>, the best way you can help is to submit a fix to
|
||||
the IOCCC website. See
|
||||
the IOCCC website. See the
|
||||
FAQ on “<a href="#fix_web_site">fixing the website</a>”
|
||||
for information on submitting fixes
|
||||
to the IOCCC website.</p>
|
||||
@@ -3128,14 +3131,14 @@ to <a href="https://github.com/ioccc-src/winner/issues/new">open a new IOCCC iss
|
||||
</div>
|
||||
</div>
|
||||
<p>For IOCCC website problems that relate to a particular IOCCC entry, please
|
||||
see
|
||||
see the
|
||||
FAQ on “<a href="#fix_an_entry">fixing an entry</a>”
|
||||
for information on how submit a fix to an IOCCC entry.</p>
|
||||
<p>You may open a <a href="https://github.com/ioccc-src/winner/pulls">GitHub pull request</a>
|
||||
against the <a href="https://github.com/ioccc-src/winner/branches">master branch</a>
|
||||
of the <a href="https://github.com/ioccc-src/winner">ioccc-src/winner repo</a>
|
||||
to submit a fix.</p>
|
||||
<p>Please see
|
||||
<p>Please see the
|
||||
FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.
|
||||
See also the
|
||||
FAQ on “<a href="#pull_request">GitHub pull request</a>”
|
||||
@@ -3163,7 +3166,7 @@ AND then run <code>make www</code> 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.</p>
|
||||
<p>Please see
|
||||
<p>Please see the
|
||||
FAQ on “<a href="#fix_an_entry">fixing an entry</a>”.</p>
|
||||
<p>See also the
|
||||
FAQ on “<a href="#pull_request">GitHub pull request</a>”
|
||||
|
||||
@@ -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.
|
||||
</div>
|
||||
|
||||
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).
|
||||
</div>
|
||||
|
||||
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
|
||||
|
||||
+1
-1
@@ -435,7 +435,7 @@ FAQ on “<a href="faq.html#menus">website menus</a>”.</p>
|
||||
</ul>
|
||||
<h1 id="entering-the-contest">Entering the Contest</h1>
|
||||
<p>View the <a href="status.html">current status of the IOCCC</a> to see of the IOCCC is open for submissions.</p>
|
||||
<p>See
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#submit">how to submit</a>”
|
||||
for more information.</p>
|
||||
<h1 id="important-disclaimer">Important Disclaimer</h1>
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -392,7 +392,7 @@
|
||||
<h3 id="please-follow-the-ioccc-on-mastodon">Please follow the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h3>
|
||||
<p>We use Mastodon to make minor announcements, in addition to announcing
|
||||
major events such as the opening of a new IOCCC, or who won.</p>
|
||||
<p>See
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#try_mastodon">Mastodon</a>”
|
||||
for more information on Mastodon.</p>
|
||||
<h1 id="news">News</h1>
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -477,7 +477,7 @@ The submit URL should be active on or slightly before <strong>2024-MMM-DD HH:MM:
|
||||
<p class="leftbar">
|
||||
The <a href="rules.html">IOCCC rules</a>, <a href="guidelines.html">IOCCC
|
||||
guidelines</a> will be available on the <a href="https://www.ioccc.org">Official IOCCC
|
||||
website</a> on or slightly before start of this IOCCC. Please check
|
||||
website</a> on or slightly before start of this IOCCC. Please check our
|
||||
FAQ on “<a href="../faq.html#submit">how to submit</a>”
|
||||
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 (‘<code>feathers are stuck in the
|
||||
<code>mkiocccentry(1)</code></strong>, then it is very possibly a bug in one of the tools and you
|
||||
should <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E">report it as a bug at the mkiocccentry issues
|
||||
page</a>. <strong>PLEASE run the
|
||||
<code>bug_report.sh</code> script to help us out here!</strong> See
|
||||
<code>bug_report.sh</code> script to help us out here!</strong> See the
|
||||
FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
@@ -957,7 +957,7 @@ would prevent this from happening as it would not create such a file anyway. If
|
||||
<code>mkiocccentry(1)</code> was used it would rather suggest a bug in one of the tools and
|
||||
you should <a href="https://github.com/ioccc-src/mkiocccentry/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBug%5D+%3Ctitle%3E">report it as a bug at the mkiocccentry issues
|
||||
page</a>.
|
||||
See
|
||||
See the
|
||||
FAQ on “<a href="../faq.html#mkiocccentry_bugs">report mkiocccentry bugs</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
@@ -1047,7 +1047,7 @@ by modifying the <code>CSTD</code> Makefile variable. For example, to use <code>
|
||||
<pre><code> CSTD= -std=c17</code></pre>
|
||||
<p class="leftbar">
|
||||
For compilers, such as <code>clang</code>, that have the <code>-Weverything</code> 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 “<a href="../faq.html#weverything">clang -Weverything</a>”.
|
||||
We do <strong>NOT</strong> recommend that you put
|
||||
the use of <code>-Weverything</code> into your submission’s <code>Makefile</code> for the reasons
|
||||
@@ -1887,7 +1887,7 @@ It has been shown that receiving <strong>anonymous</strong> gifts provides the
|
||||
<a href="../judges.html">IOCCC judges</a> help make the <a href="../index.html">IOCCC</a> better for everyone. :-)
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
See
|
||||
See the
|
||||
FAQ on “<a href="../faq.html#support">support the IOCCC</a>”.
|
||||
</p>
|
||||
<p>More often than not, we select a small submission (usually one line) and a
|
||||
|
||||
+6
-6
@@ -116,7 +116,7 @@ The submit URL should be active on or slightly before **2024-MMM-DD HH:MM:SS UTC
|
||||
<p class="leftbar">
|
||||
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)".
|
||||
</p>
|
||||
|
||||
@@ -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)".
|
||||
</p>
|
||||
|
||||
@@ -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)".
|
||||
</p>
|
||||
|
||||
@@ -755,7 +755,7 @@ by modifying the `CSTD` Makefile variable. For example, to use `c17` instead:
|
||||
|
||||
<p class="leftbar">
|
||||
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
|
||||
</p>
|
||||
|
||||
<p class="leftbar">
|
||||
See
|
||||
See the
|
||||
FAQ on "[support the IOCCC](../faq.html#support)".
|
||||
</p>
|
||||
|
||||
|
||||
+5
-6
@@ -474,7 +474,7 @@ provisional <strong>BETA</strong> versions and <strong>may be adjusted <em>AT AN
|
||||
<p>When the IOCCC is open, the submission URL is:
|
||||
<a href="https://submit.ioccc.org">https://submit.ioccc.org</a>; at all other
|
||||
times that link is likely to be unresponsive.</p>
|
||||
<p>Please check the
|
||||
<p>Please review our
|
||||
FAQ on “<a href="../faq.html#submit">how to submit</a>”
|
||||
for <strong>important information</strong> on how to submit to the IOCCC.</p>
|
||||
<p class="leftbar">
|
||||
@@ -572,8 +572,7 @@ as a command like argument to the <code>iocccsize(1)</code> tool. For example:
|
||||
<div id="rule3">
|
||||
<h2 id="rule-3">Rule 3</h2>
|
||||
</div>
|
||||
<p>Submissions should be performed using the instructions outlined at:
|
||||
the
|
||||
<p>Submissions should be performed using the instructions outlined in our
|
||||
FAQ on “<a href="../faq.html#submit">how to submit</a>”</p>
|
||||
<p>To submit to an open IOCCC, you must use the <a href="https://submit.ioccc.org/">IOCCC submit
|
||||
server</a>. Unless the IOCCC is open, that link will
|
||||
@@ -700,7 +699,7 @@ In order to register for the IOCCC, you <strong>MUST</strong> have a valid email
|
||||
enough time for one automated exchange of email as part of your
|
||||
submission.</p>
|
||||
<p class="leftbar">
|
||||
See
|
||||
See the
|
||||
FAQ on “<a href="../faq.html#register">how to register</a>”
|
||||
for details.
|
||||
</p>
|
||||
@@ -839,7 +838,7 @@ for help.
|
||||
The <code>remarks.md</code> <strong>MUST</strong> be a <strong>non</strong>-empty file in markdown form. See also
|
||||
<a href="#rule18">Rule 18</a> and our
|
||||
FAQ on “<a href="../faq.html#remarks_md">remarks.md</a>”
|
||||
and the
|
||||
and our
|
||||
FAQ on “<a href="../faq.html#markdown">markdown practices</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
@@ -966,7 +965,7 @@ If you run into a problem with one or more of these tools, <strong>PLEASE</stron
|
||||
as a bug at the mkiocccentry issues
|
||||
page</a>,
|
||||
<strong>making sure to run <code>bug_report.sh</code></strong>. See the <a href="guidelines.html">guidelines</a>
|
||||
for help here and also read
|
||||
for help here and also read our
|
||||
FAQ on “<a href="../faq.html#mkiocccentry_bugs">mkiocccentry repo bugs</a>”.
|
||||
</p>
|
||||
<p class="leftbar">
|
||||
|
||||
+5
-6
@@ -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
|
||||
</div>
|
||||
|
||||
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.
|
||||
|
||||
<p class="leftbar">
|
||||
See
|
||||
See the
|
||||
FAQ on "[how to register](../faq.html#register)"
|
||||
for details.
|
||||
</p>
|
||||
@@ -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)".
|
||||
</p>
|
||||
|
||||
@@ -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)".
|
||||
</p>
|
||||
|
||||
|
||||
+64
-41
@@ -549,7 +549,8 @@ returning to the shell. The original code does not have this change.</p>
|
||||
versions of <code>clang</code> object to the number of args of <code>main()</code>, 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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Cody also added the script <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1985/august/primes.sh">primes.sh</a> which allows one
|
||||
@@ -682,11 +683,12 @@ should they object to <code>main()</code> having only one arg.</p>
|
||||
<h2 id="winning-entry-1986hague">Winning entry: <a href="1986/hague/index.html">1986/hague</a></h2>
|
||||
<h3 id="winning-entry-source-code-hague.c">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1986/hague/hague.c">hague.c</a></h3>
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets()</code>. See
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets()</code>.
|
||||
Cody also added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1986/hague/try.sh">try.sh</a> script which also feeds to the
|
||||
program the <code>input.txt</code> text file that Cody added.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<div id="1986_holloway">
|
||||
<h2 id="winning-entry-1986holloway">Winning entry: <a href="1986/holloway/index.html">1986/holloway</a></h2>
|
||||
<h3 id="winning-entry-source-code-holloway.c">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1986/holloway/holloway.c">holloway.c</a></h3>
|
||||
@@ -894,7 +896,8 @@ size constraints of the contest).</p>
|
||||
<h2 id="winning-entry-1987wall">Winning entry: <a href="1987/wall/index.html">1987/wall</a></h2>
|
||||
<h3 id="winning-entry-source-code-wall.c-1">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1987/wall/wall.c">wall.c</a></h3>
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code>. See
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<p>Cody also added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1987/wall/try.sh">try.sh</a> script.</p>
|
||||
@@ -1009,7 +1012,8 @@ same code, just a <code>p</code> instead of an <code>m</code> in the name. Addit
|
||||
<h2 id="winning-entry-1988reddy">Winning entry: <a href="1988/reddy/index.html">1988/reddy</a></h2>
|
||||
<h3 id="winning-entry-source-code-reddy.c">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/reddy/reddy.c">reddy.c</a></h3>
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code>. See
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<div id="1988_spinellis">
|
||||
@@ -1270,7 +1274,8 @@ judges was retained.</p>
|
||||
</div>
|
||||
<p><a href="#yusuke">Yusuke</a> got this to work in modern systems (it previously resulted in a bus
|
||||
error).</p>
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code>. See
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<div id="1990_dds">
|
||||
@@ -1285,7 +1290,8 @@ more like the original in this way by redefining <code>free</code> to have the c
|
||||
operator itself.</p>
|
||||
<p>Cody fixed another compiler error by removing the erroneous prototype to
|
||||
<code>fopen(3)</code>. Cody also changed a <code>char *</code> used for file I/O to be a proper <code>FILE *</code> and fixed a typo in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/dds/LANDER.BAS">LANDER.BAS</a>.</p>
|
||||
<p>Cody also made this use <code>fgets(3)</code>. See
|
||||
<p>Cody also made this use <code>fgets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<div id="1990_dg">
|
||||
@@ -1347,7 +1353,8 @@ author.</p>
|
||||
<p>Cody also changed the code (in both versions) to use <code>fgets(3)</code> instead of
|
||||
<code>gets(3)</code> so one would not get a warning about the use of <code>gets(3)</code> 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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for more details on why this change was
|
||||
done more generally.</p>
|
||||
@@ -1370,7 +1377,8 @@ but as he was testing the <code>fibonacci.c</code> bug he ended up changing it a
|
||||
<pre><code> if (a[1]==NULL||a[2]==NULL||a[3]==NULL||a[4]==NULL||a[5]==NULL) return 1;</code></pre>
|
||||
<p>be changed to just test the value of <code>A</code> when <code>a</code> is argv and <code>A</code> is argc? You
|
||||
tell us!</p>
|
||||
<p>Cody also changed the code to use <code>fgets(3)</code>. See
|
||||
<p>Cody also changed the code to use <code>fgets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<p>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.</p>
|
||||
condition (the <code>char *s</code> had to be changed to <code>char s[]</code>) and he also made it
|
||||
and the generated code work for <code>clang</code>.</p>
|
||||
<p>Furthermore Cody changed it so that the C from the BASIC uses <code>fgets()</code>, not
|
||||
<code>gets()</code>. See
|
||||
<code>gets()</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<p>For the magic of <code>clang</code> (which was done manually except the returning a value
|
||||
@@ -1642,11 +1651,11 @@ true of another change as further below.</p>
|
||||
<pre><code> - putc("}|uutsrq`_^bji`[Zkediml[PO]a_M__]ISOYIRGTNR"[i]+i-9,stderr);
|
||||
+ putc(i["}|uutsrq`_^bji`[Zkediml[PO]a_M__]ISOYIRGTNR"]+i-9,stderr);</code></pre>
|
||||
<p>though it’s questionable how much more (if at all) obscure that is :-)</p>
|
||||
<p>Cody also changed the location that it used <code>gets()</code> to be <code>fgets(3)</code>.
|
||||
See
|
||||
<p>Cody also changed the location that it used <code>gets()</code> to be <code>fgets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
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.</p>
|
||||
<p>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).</p>
|
||||
<p>One might think that simply changing the <code>gets(3)</code> to <code>fgets(3)</code> (with <code>stdin</code>)
|
||||
@@ -1770,7 +1779,8 @@ start and end character.</p>
|
||||
defect with the number of args to <code>main()</code> 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 <code>clang</code> or the ANSI C committee end up further
|
||||
changing this. See
|
||||
changing this.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Yusuke also noted that there is a bug in the program where right after starting
|
||||
@@ -1785,7 +1795,8 @@ it works (see <a href="1992/lush/index.html#judges-remarks">Judges’ remarks in
|
||||
file</a>) this will not work with <code>clang</code>.</p>
|
||||
<p><a href="#cody">Cody</a> also provided the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/lush/lush.sh">lush.sh</a> script to
|
||||
demonstrate it as using make was problematic.</p>
|
||||
<p>Cody made it use <code>fgets()</code> instead of <code>gets()</code>. See
|
||||
<p>Cody made it use <code>fgets()</code> instead of <code>gets()</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<p>NOTE: this entry cannot work with <code>clang</code> due to different compiler messages (it
|
||||
@@ -1959,7 +1970,8 @@ compile time. See the index.html for details.</p>
|
||||
<h2 id="winning-entry-1993schnitzi">Winning entry: <a href="1993/schnitzi/index.html">1993/schnitzi</a></h2>
|
||||
<h3 id="winning-entry-source-code-schnitzi.c">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1993/schnitzi/schnitzi.c">schnitzi.c</a></h3>
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code> not <code>gets(3)</code>. See
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code> not <code>gets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<div id="1993_vanb">
|
||||
@@ -2049,10 +2061,10 @@ comma operator was needed.</p>
|
||||
<p>Cody also fixed it for <code>clang</code> under Linux which objected to incompatible pointer
|
||||
type (because <code>time(2)</code> takes a <code>time_t *</code> which in some systems is a <code>long *</code>
|
||||
but what was being passed to it is an <code>int</code>).</p>
|
||||
<p>Cody also changed the entry to use <code>fgets(3)</code> instead of <code>gets(3)</code>.
|
||||
(See
|
||||
<p>Cody also changed the entry to use <code>fgets(3)</code> instead of <code>gets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.)</p>
|
||||
for why this was done.</p>
|
||||
<p>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), <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/tvr/try.alt.bw.sh">try.alt.bw.sh</a>, 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).</p>
|
||||
<p>Cody also made this use <code>fgets(3)</code> instead of <code>gets(3)</code>.
|
||||
See
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
]for why this was done.
|
||||
In this case the newline had
|
||||
<p>Cody also made this use <code>fgets(3)</code> instead of <code>gets(3)</code>.</p>
|
||||
<p>In this case the newline had
|
||||
to be terminated but it was a pretty straightforward fix. <code>gets()</code> was defined
|
||||
to use <code>fgets()</code> and the inclusion of <code>stdio.h</code> 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 <code>fgets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<div id="1994_weisberg">
|
||||
<h2 id="winning-entry-1994weisberg">Winning entry: <a href="1994/weisberg/index.html">1994/weisberg</a></h2>
|
||||
<h3 id="winning-entry-source-code-weisberg.c">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/weisberg/weisberg.c">weisberg.c</a></h3>
|
||||
@@ -2164,7 +2176,8 @@ details on this.</p>
|
||||
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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<div id="1995_dodsond1">
|
||||
@@ -2381,7 +2394,8 @@ versions of <code>clang</code> 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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Cody also added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/bas1/bas1.sh">bas1.sh</a> script to simplify running the
|
||||
@@ -2451,7 +2465,8 @@ versions of <code>clang</code> complain about the number of args to <code>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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>In some versions of <code>clang</code> <code>-Wno-int-conversion</code> had to be added to the
|
||||
@@ -2550,7 +2565,8 @@ occurs.</p>
|
||||
<p>Cody made <code>main()</code> have two args out of an abundance of caution as some versions
|
||||
of <code>clang</code> say that <code>main()</code> 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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Cody added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1998/schweikh3/try.sh">try.sh</a> script to make it easier to try
|
||||
@@ -2589,11 +2605,11 @@ commands that we recommended.</p>
|
||||
<h3 id="winning-entry-source-code-anderson.c">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/anderson//anderson.c">anderson.c</a></h3>
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a> changed this entry to use <code>fgets(3)</code> instead of <code>gets(3)</code>.
|
||||
See
|
||||
This involved changing the <code>K</code> arg to <code>gets(3)</code> to <code>&K</code> in <code>fgets(3)</code>.
|
||||
Cody also added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/anderson/try.sh">try.sh</a> script.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.
|
||||
This involved changing the <code>K</code> arg to <code>gets(3)</code> to <code>&K</code> in <code>fgets(3)</code>.</p>
|
||||
<p>Cody also added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/anderson/try.sh">try.sh</a> script.</p>
|
||||
for why this was done.</p>
|
||||
<div id="2000_bmeyer">
|
||||
<h2 id="winning-entry-2000bmeyer">Winning entry: <a href="2000/bmeyer/index.html">2000/bmeyer</a></h2>
|
||||
<h3 id="winning-entry-source-code-bmeyer.c">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/bmeyer//bmeyer.c">bmeyer.c</a></h3>
|
||||
@@ -3082,7 +3098,8 @@ a lot of numbers this will be harder to see).</p>
|
||||
discovered it will not work otherwise.</p>
|
||||
<p>Cody, out of an abundance of caution for <code>clang</code>, added a second arg to <code>main()</code>
|
||||
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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Cody also added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/kopczynski/try.sh">try.sh</a> script and various data
|
||||
@@ -3107,7 +3124,8 @@ chose the word <code>IOCCC</code> instead of <code>AAA</code>).</p>
|
||||
<h2 id="winning-entry-2004schnitzi">Winning entry: <a href="2004/schnitzi/index.html">2004/schnitzi</a></h2>
|
||||
<h3 id="winning-entry-source-code-schnitzi.c-4">Winning entry source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/schnitzi//schnitzi.c">schnitzi.c</a></h3>
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code>. See
|
||||
<p><a href="#cody">Cody</a> made this use <code>fgets(3)</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
|
||||
for why this was done.</p>
|
||||
<p>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.</p>
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a>, out of an abundance of caution for <code>clang</code>’s defects, made <code>main()</code> have
|
||||
2 args instead of 1 as some versions report that <code>main()</code> 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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Cody also added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/sykes2/try.sh">try.sh</a> script for easier use of the
|
||||
@@ -3530,7 +3549,8 @@ We’re not able to test this.</p>
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a>, out of an abundance of caution, added a second arg to <code>main()</code> as some
|
||||
versions of <code>clang</code> complain about not only the type of each arg to <code>main()</code> but
|
||||
the number of args as well. See
|
||||
the number of args as well.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Cody also added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/borsanyi/try.sh">try.sh</a> script.</p>
|
||||
@@ -3702,7 +3722,8 @@ everything, filtered through less.</p>
|
||||
<p>Cody also changed <code>argv</code> to be not <code>const char **</code> but <code>char **</code>, mostly out of an
|
||||
abundance of caution in case <code>clang</code>, which already imposes restrictions on the
|
||||
types of args to <code>main()</code> including to do with <code>char **</code>, decides to further
|
||||
restrict them. See
|
||||
restrict them.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Cody also restored the original code from the archive.</p>
|
||||
@@ -3917,7 +3938,8 @@ also appear to be an issue with the script even if you know of <code>convert</co
|
||||
</div>
|
||||
<p><a href="#cody">Cody</a> added the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/endoh3/try.sh">try.sh</a> script.</p>
|
||||
<p>Cody also (out of an abundance of caution for <code>clang(1)</code> which is strict with
|
||||
arg type and count to <code>main()</code>) added a second (unused) arg to <code>main()</code>. See
|
||||
arg type and count to <code>main()</code>) added a second (unused) arg to <code>main()</code>.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<div id="2013_endoh4">
|
||||
@@ -4272,7 +4294,8 @@ the repo.</p>
|
||||
some versions of <code>clang</code> object to the number of args of <code>main()</code>, 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.</p>
|
||||
<p>See the
|
||||
FAQ on “<a href="faq.html#arg_count">main function args</a>”
|
||||
for more details.</p>
|
||||
<p>Cody also added explicit linking of libm (<code>-lm</code>) for systems that do not do this
|
||||
|
||||
+87
-40
@@ -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)
|
||||
</div>
|
||||
|
||||
[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.
|
||||
|
||||
|
||||
<div id="1986_holloway">
|
||||
## 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)
|
||||
</div>
|
||||
|
||||
[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)
|
||||
</div>
|
||||
|
||||
[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.
|
||||
|
||||
|
||||
|
||||
<div id="1988_spinellis">
|
||||
## 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)
|
||||
</div>
|
||||
|
||||
[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.
|
||||
|
||||
|
||||
<div id="1994_weisberg">
|
||||
## 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.
|
||||
|
||||
|
||||
|
||||
<div id="1995_dodsond1">
|
||||
## 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.
|
||||
</div>
|
||||
|
||||
[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.
|
||||
|
||||
|
||||
<div id="2000_bmeyer">
|
||||
@@ -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)
|
||||
</div>
|
||||
|
||||
[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.
|
||||
|
||||
|
||||
|
||||
|
||||
<div id="2013_endoh4">
|
||||
## 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.
|
||||
|
||||
|
||||
Reference in new issue
Block a user