mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Various fixes and updates

Browse Source 
The links to rules should all be good. This includes in news.html,
quick-start.html, next/submit.html, 2024/index.html (it had been
modified to refer to next/rules.html instead of 2024/rules.html) as well
as the guidelines and rules themselves (under next/).

Various typo fixes. I'm afraid there are likely others but I must let
others deal with that as I am out of time.

Removed FAQ about mastodon push notifications. When I added the FAQ
about push notifications for mastodon I was incorrect. The web browser
interface suggests it but I never got a push notification even before
Apple broke them. There seems to be no way at this time to get them. I
note that there was a screenshot in the FAQ but this file still is in
the repo possibly.

I regenerated the html files but it's possible I forgot to do one at the
last minute.
This commit is contained in:
Cody Boone Ferguson committed 2025-11-29 12:03:55 -08:00
1 parent 28349bfb95
commit 6c49bc8955
14 files changed
+161 -3140
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2024/README.md
+3 -3
View File
@@ -77,7 +77,7 @@ become more skilled in the programming in the C language.
We were pleased to observe that while the [IOCCC size limit](../faq.html#size_rule_history)
increased by about 21%, we received many submissions that were well under the new
[Rule 2 Size](../next/rules.html#rule-2-size) including a fair number of quality
[Rule 2](rules.html#rule2) including a fair number of quality
small and medium sized submissions. Half of the **IOCCC28 winners** were less than
_2/3 of the size limit_, and 10 of the **IOCCC28 winners** were less than
_1/2 of the size limit_!
@@ -85,10 +85,10 @@ _1/2 of the size limit_!
**IMPORTANT NOTE**: The [IOCCC size limit](../faq.html#size_rule_history) increase for **IOCCC28**
was the first size increase in over 10 years. Given the quality of submissions we received
that were well under the limit, we do **NOT** expect to change the
[Rule 2 Size](../next/rules.html#rule-2-size) for **at least another 10 years** (and likely longer).
[Rule 2](rules.html#rule2) for **at least another 10 years** (and likely longer).
**IMPORTANT HINT**: Only 3 of the 23 **IOCCC28 winners** came close to the [Rule
2 Size](../next/rules.html#rule-2-size). Large code size isn't everything. :-)
2](rules.html#rule2). Large code size isn't everything. :-)
Those submitting to future contents should **take a careful note** of that fact.
2024/index.html
+4 -4
View File
@@ -513,16 +513,16 @@ become more skilled in the programming in the C language.</p>
<h3 id="code-size-and-rule-2">Code size and Rule 2</h3>
<p>We were pleased to observe that while the <a href="../faq.html#size_rule_history">IOCCC size limit</a>
increased by about 21%, we received many submissions that were well under the new
<a href="../next/rules.html#rule-2-size">Rule 2 Size</a> including a fair number of quality
<a href="rules.html#rule2">Rule 2</a> including a fair number of quality
small and medium sized submissions. Half of the <strong>IOCCC28 winners</strong> were less than
<em>2/3 of the size limit</em>, and 10 of the <strong>IOCCC28 winners</strong> were less than
<em>1/2 of the size limit</em>!</p>
<p><strong>IMPORTANT NOTE</strong>: The <a href="../faq.html#size_rule_history">IOCCC size limit</a> increase for <strong>IOCCC28</strong>
was the first size increase in over 10 years. Given the quality of submissions we received
that were well under the limit, we do <strong>NOT</strong> expect to change the
<a href="../next/rules.html#rule-2-size">Rule 2 Size</a> for <strong>at least another 10 years</strong> (and likely longer).</p>
<p><strong>IMPORTANT HINT</strong>: Only 3 of the 23 <strong>IOCCC28 winners</strong> came close to the <a href="../next/rules.html#rule-2-size">Rule
2 Size</a>. Large code size isn’t everything. :-)
<a href="rules.html#rule2">Rule 2</a> for <strong>at least another 10 years</strong> (and likely longer).</p>
<p><strong>IMPORTANT HINT</strong>: Only 3 of the 23 <strong>IOCCC28 winners</strong> came close to the <a href="rules.html#rule2">Rule
2</a>. Large code size isn’t everything. :-)
Those submitting to future contents should <strong>take a careful note</strong> of that fact.</p>
<h3 id="rules-and-guidelines-for-this-contest">Rules and Guidelines for this contest</h3>
<p>Here are the final versions of the IOCCC rules and guidelines that were in
faq.html
+26 -59
View File
@@ -493,7 +493,7 @@
<li><strong>Q 2.1</strong>: <a class="normal" href="#feedback">How can I comment or make a suggestion on IOCCC rules, guidelines and tools?</a></li>
<li><strong>Q 2.2</strong>: <a class="normal" href="#warnings">Are there any compiler warnings that I should not worry about in my submissions?</a></li>
<li><strong>Q 2.3</strong>: <a class="normal" href="#frequent-themes">What types of entries have been frequently submitted to the IOCCC?</a></li>
<li><strong>Q 2.4</strong>: <a class="normal" href="#rule_2_broken">How did an entry win the IOCCC that breaks Rule 2 - Size?</a></li>
<li><strong>Q 2.4</strong>: <a class="normal" href="#rule_2_broken">How did an entry win the IOCCC that breaks Rule 2 - Size Limit?</a></li>
<li><strong>Q 2.5</strong>: <a class="normal" href="#submissions">How many submissions do the judges receive for a given IOCCC?</a></li>
<li><strong>Q 2.6</strong>: <a class="normal" href="#judging_time">How much time does it take to judge the contest?</a></li>
<li><strong>Q 2.7</strong>: <a class="normal" href="#judging_rounds">How many judging rounds do you have?</a></li>
@@ -590,10 +590,7 @@
<li><strong>Q 10.3</strong>: <a class="normal" href="#dot_files"> What is the purpose of the <code>.top</code>, <code>.allyear</code>, <code>.year</code> and <code>.path</code> files?</a></li>
<li><strong>Q 10.4</strong>: <a class="normal" href="#terms"> What is the current meaning of the IOCCC terms Author, Entry, and Submission?</a></li>
<li><strong>Q 10.5</strong>: <a class="normal" href="#licence">Am I allowed to use IOCCC content?</a></li>
<li><strong>Q 10.6</strong>: <a class="normal" href="#try_mastodon">What is Mastodon and why does the IOCCC use it?</a>
<ul>
<li><strong>Q 10.6.1</strong>: <a class="normal" href="#mastodon_notifications">How can I get push notifications when the judges post something on mastodon?</a></li>
</ul></li>
<li><strong>Q 10.6</strong>: <a class="normal" href="#try_mastodon">What is Mastodon and why does the IOCCC use it?</a></li>
<li><strong>Q 10.7</strong>: <a class="normal" href="#tabstops">How do I set certain tabstops for viewing source code in vi(m)?</a></li>
<li><strong>Q 10.8</strong>: <a class="normal" href="#menus">How do the menus on the website work and what can I do if they don’t work?</a></li>
<li><strong>Q 10.9</strong>: <a class="normal" href="#author-information">How do I find more information about a winning author of an entry?</a></li>
@@ -986,7 +983,8 @@ and
itself.</p>
<p>Do remember that if your submission requires different filenames, then you
<strong>MUST</strong> make a <strong>COPY</strong> of them in your <code>Makefile</code>. See also
<a href="next/rules.html#rule-5---integrity">Rule 5 - Integrity</a>.</p>
<a href="next/rules.html#rule5-modifying-files">Rule 5 - Do NOT modify submitted files or filenames or parent
directories</a>.</p>
<p>Jump to: <a href="#">top</a></p>
<hr style="width:50%;text-align:left;margin-left:0">
<hr style="width:50%;text-align:left;margin-left:0">
@@ -1328,10 +1326,11 @@ modes, it also verifies them after the fact and if they are not correct it is an
<strong>error</strong>.</p>
<p>If you do need different permissions, then see the
FAQ on “<a href="#file_perms">file permissions</a>”. Also keep in mind
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>,
<a href="next/rules.html#rule-5---integrity">Rule 5 - Integrity</a>,
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>,
<a href="next/rules.html#rule5-modifying-files">Rule 5 - Do NOT modify submitted files or filenames or parent
directories</a>,
and
<a href="next/rules.html#rule-16---anonymous">Rule 16 - Anonymous</a>.</p>
<a href="next/rules.html#rule16-anonymous-judging">Rule 16 - Anonymous judging</a>.</p>
<p>The <code>txzchk(1)</code> tool will also verify file/directory permissions (and many other
things) for you, and so will <code>chksubmit(1)</code> (along with other checks on files and
directories in your submission directory, including the two required JSON files,
@@ -1344,7 +1343,7 @@ page</a>.</p>
will run <code>fnamchk(1)</code> as part of its algorithm. If you use <code>mkiocccentry(1)</code>
there should be no problem but if you were to package things manually it is
possible there could be a problem and this poses a big risk of violating
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>
or
<a href="next/rules.html#rule17">Rule 17 - Use mkiocccentry</a>.</p>
<p>The <code>fnamchk(1)</code>, which <code>txzchk(1)</code> executes, will verify that the
@@ -1353,7 +1352,7 @@ mismatch in what is in the tarball and the name, <code>txzchk(1)</code> will fla
discrepancy as an error and exit with non-zero.</p>
<p>These checks <strong>MUST PASS</strong>. If they do not you stand a significant chance of
having your submission rejected for violating
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>
or
<a href="next/rules.html#rule17">Rule 17 - Use mkiocccentry</a>.</p>
<div id="max-files">
@@ -1385,9 +1384,9 @@ The <code>mkiocccentry(1)</code> tool uses the v7 format. For instance you might
<pre><code> tar --format=v7 -cJf foo.txz directory</code></pre>
<hr style="width:50%;text-align:left;margin-left:0">
<p><strong>IMPORTANT</strong>: where
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>,
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>,
and
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>
and the tools from the latest
release of the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>
conflict, the <a href="judges.html">IOCCC judges</a> will use their best judgment which
@@ -1422,7 +1421,7 @@ page</a>,
for help here and also read our
FAQ on “<a href="#mkiocccentry_bugs">mkiocccentry repo bugs</a>”.</p>
<p>At the risk of stating the obvious: submissions that violate
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>,
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>,
or
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>
<strong>WILL BE REJECTED</strong>, so <strong>BE SURE</strong> to use the latest release of the
@@ -1903,7 +1902,7 @@ of the same theme.</p>
<p>Jump to: <a href="#">top</a></p>
<div id="rule_2_broken">
<div id="rule_breaking_entry">
<h3 id="q-2.4-how-did-an-entry-win-the-ioccc-that-breaks-rule-2---size">Q 2.4: How did an entry win the IOCCC that breaks Rule 2 - Size?</h3>
<h3 id="q-2.4-how-did-an-entry-win-the-ioccc-that-breaks-rule-2---size-restrictions">Q 2.4: How did an entry win the IOCCC that breaks Rule 2 - Size restrictions?</h3>
</div>
</div>
<p>As entries have been fixed it is entirely possible that some of the entries no
@@ -2120,7 +2119,7 @@ two JSON files, <code>.auth.json</code> and <code>.info.json</code> as well as t
<code>.info.json</code> manifest. (Okay there is an option to skip files but this is for
the judges <strong>ONLY</strong>; use of this option to validate your submission puts you at
a great risk of violating
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>,
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>,
or
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>!).</p>
<p>As an example, if your submission directory is
@@ -2142,7 +2141,7 @@ FAQ on “<a href="#auth_json">.auth.json</a>”
and the
FAQ on “<a href="#info_json">.info.json</a>”
as well as
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>,
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>,
and
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>
for more information.</p>
@@ -2424,7 +2423,7 @@ will use it on the submission directory as part of the judging process.</p>
is reported invalid by <code>chksubmit(1)</code>, or if your submission directory is
reported invalid by <code>chksubmit(1)</code>, your submission will almost certainly be
rejected for violating the <a href="next/rules.html">Rules</a> and in particular
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>,
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>,
and
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p>
<p>An obvious example where <code>chksubmit(1)</code> would fail to validate <code>.auth.json</code> is if
@@ -2435,7 +2434,7 @@ out of range (see above for list). Two more examples would be if a field is
missing or if an unknown filed is in the file. In these cases (and any others
that must be established as valid by <code>chksubmit(1)</code>) your submission would be
rejected for violating
<a href="next/rules.html#rule-4---files">Rule 4 - Files</a>,
<a href="next/rules.html#rule4-required-files">Rule 4 - Required files</a>,
and
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>
and in particular
@@ -2608,17 +2607,17 @@ validate your filename, or if you have the wrong directory name in the
tarball, this will be flaggd.</p></li>
<li><p><code>rule_2a_size</code> (number)</p>
<ul>
<li>The size calculated of <a href="next/rules.html#rule-2a-gross-size">Rule 2a Gross Size</a>.</li>
<li>The size calculated of <a href="next/rules.html#rule2a-gross-size">Rule 2a - Gross Size</a>.</li>
</ul>
<p><strong>IMPORTANT:</strong> if this violates <a href="next/rules.html#rule2a">Rule 2a</a> you stand a great
chance of having your submission rejected for violating the
<a href="next/rules.html">Rules</a>!</p></li>
<li><p><code>rule_2b_size</code> (number)</p>
<ul>
<li>The size calculated of <a href="next/rules.html#rule-2b-net-size">Rule 2b Next Size</a>.</li>
<li>The size calculated of <a href="next/rules.html#rule2b-net-size">Rule 2b - Net Size</a>.</li>
</ul>
<p><strong>IMPORTANT:</strong> if this violates
<a href="next/rules.html#rule-2b-net-size">Rule 2b Next Size</a>
<a href="next/rules.html#rule2b-net-size">Rule 2b Net Size</a>
you stand a great
chance of having your submission rejected for violating the
<a href="next/rules.html">Rules</a>!</p></li>
@@ -2629,11 +2628,11 @@ chance of having your submission rejected for violating the
<li><p><code>rule_2a_override</code> (boolean)</p>
<ul>
<li><code>true</code> if user overrides warning of
<a href="next/rules.html#rule-2a-gross-size">Rule 2a Gross Size</a>
<a href="next/rules.html#rule2a-gross-size">Rule 2a - Gross Size</a>
violation, else <code>false</code>.</li>
</ul>
<p><strong>IMPORTANT:</strong> if the
<a href="next/rules.html#rule-2a-gross-size">Rule 2a Gross Size</a>
<a href="next/rules.html#rule2a-gross-size">Rule 2a - Gross Size</a>
calculated size is <strong>NOT</strong>
violated but this is <code>true</code> then you stand a good chance of having your
submission rejected for violating
@@ -2641,43 +2640,27 @@ submission rejected for violating
<li><p><code>rule_2a_mismatch</code> (boolean)</p>
<ul>
<li><code>true</code> if
<a href="next/rules.html#rule-2a-gross-size">Rule 2a Gross Size</a>
<a href="next/rules.html#rule2a-gross-size">Rule 2a - Gross Size</a>
calculated size is not the
same as the file size.</li>
</ul></li>
<li><p><code>rule_2b_override</code> (boolean)</p>
<ul>
<li><code>true</code> if user overrides warning of
<a href="next/rules.html#rule-2b-net-size">Rule 2b Next Size</a>
<a href="next/rules.html#rule2b-net-size">Rule 2b - Net Size</a>
violation, else <code>false</code>.</li>
</ul>
<p><strong>IMPORTANT:</strong> if the
<a href="next/rules.html#rule-2b-net-size">Rule 2b Next Size</a>
<a href="next/rules.html#rule2b-net-size">Rule 2b - Net Size</a>
calculated size is <strong>NOT</strong>
violated but this is <code>true</code> then you stand a good chance of having your
submission rejected for violating
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p></li>
<li><p><code>highbit_warning</code> (boolean)</p>
<ul>
<li><code>true</code> if <code>iocccsize</code> detects a high bit (unescaped octets with the high
bit set - octet value &gt;= 128); see
<a href="next/rules.html#rule-12---utf-8">Rule 12 - UTF-8</a>,
else <code>false</code>.</li>
</ul></li>
<li><p><code>nul_warning</code> (boolean)</p>
<ul>
<li><code>true</code> if <code>iocccsize</code> detects a NUL character in the <code>prog.c</code>, else
<code>false</code>.</li>
</ul></li>
<li><p><code>trigraph_warning</code> (boolean)</p>
<ul>
<li><code>true</code> if <code>iocccsize</code> detects an unknown or invalid trigraph in
<code>prog.c</code>, else <code>false</code>.</li>
</ul></li>
<li><p><code>wordbuf_warning</code> (boolean)</p>
<ul>
<li>This is ignored and will be removed for IOCCC29 and beyond.</li>
</ul></li>
<li><p><code>ungetc_warning</code> (boolean)</p>
<ul>
<li><code>true</code> if <code>prog.c</code> triggered an <code>ungetc(3)</code> error, else <code>false</code>.</li>
@@ -5858,22 +5841,6 @@ follow posts something so you will have to check the IOCCC feed manually.</p>
mastodon feed</a> page and/or mastodon
app from time to time to view IOCCC mastodon updates.</p>
<p>Jump to: <a href="#">top</a></p>
<div id="mastodon_notifications">
<h3 id="q-10.6.1-how-can-i-get-push-notifications-when-the-judges-post-something-on-mastodon">Q 10.6.1: How can I get push notifications when the judges post something on mastodon?</h3>
</div>
<p>To do this you need to go to the <a href="https://fosstodon.org/@ioccc">IOCCC mastodon
account</a> with a computer (it is unclear how to do
this with a mobile device, if it is even possible) and then you should see a
bell icon. Make sure it’s activated. If you mouse over it when it’s not enabled
it should look something like this, assuming of course we follow you! :-) (if
not the message about following each other won’t show up):</p>
<p><img src="png/mastodon-notifications.png"
alt="screenshot of Mastodon push notifications"
width=912 height=556></p>
<p>It is not yet clear if this only works on desktop/computers or mobile devices
too as it was only just discovered (31 July 2025) but whatever the case we
suggest you do it.</p>
<p>Jump to: <a href="#">top</a></p>
<div id="tabstops">
<h3 id="q-10.7-how-do-i-set-certain-tabstops-for-viewing-source-code-in-vim">Q 10.7: How do I set certain tabstops for viewing source code in vi(m)?</h3>
</div>
faq.md
+25 -60
View File
@@ -39,7 +39,7 @@ This is FAQ version **29.02 2025-11-29**.
- **Q 2.1**: <a class="normal" href="#feedback">How can I comment or make a suggestion on IOCCC rules, guidelines and tools?</a>
- **Q 2.2**: <a class="normal" href="#warnings">Are there any compiler warnings that I should not worry about in my submissions?</a>
- **Q 2.3**: <a class="normal" href="#frequent-themes">What types of entries have been frequently submitted to the IOCCC?</a>
- **Q 2.4**: <a class="normal" href="#rule_2_broken">How did an entry win the IOCCC that breaks Rule 2 - Size?</a>
- **Q 2.4**: <a class="normal" href="#rule_2_broken">How did an entry win the IOCCC that breaks Rule 2 - Size Limit?</a>
- **Q 2.5**: <a class="normal" href="#submissions">How many submissions do the judges receive for a given IOCCC?</a>
- **Q 2.6**: <a class="normal" href="#judging_time">How much time does it take to judge the contest?</a>
- **Q 2.7**: <a class="normal" href="#judging_rounds">How many judging rounds do you have?</a>
@@ -133,7 +133,6 @@ This is FAQ version **29.02 2025-11-29**.
- **Q 10.4**: <a class="normal" href="#terms"> What is the current meaning of the IOCCC terms Author, Entry, and Submission?</a>
- **Q 10.5**: <a class="normal" href="#licence">Am I allowed to use IOCCC content?</a>
- **Q 10.6**: <a class="normal" href="#try_mastodon">What is Mastodon and why does the IOCCC use it?</a>
- **Q 10.6.1**: <a class="normal" href="#mastodon_notifications">How can I get push notifications when the judges post something on mastodon?</a>
- **Q 10.7**: <a class="normal" href="#tabstops">How do I set certain tabstops for viewing source code in vi&lpar;m&rpar;?</a>
- **Q 10.8**: <a class="normal" href="#menus">How do the menus on the website work and what can I do if they don't work?</a>
- **Q 10.9**: <a class="normal" href="#author-information">How do I find more information about a winning author of an entry?</a>
@@ -646,7 +645,8 @@ itself.
Do remember that if your submission requires different filenames, then you
**MUST** make a **COPY** of them in your `Makefile`. See also
[Rule 5 - Integrity](next/rules.html#rule-5---integrity).
[Rule 5 - Do NOT modify submitted files or filenames or parent
directories](next/rules.html#rule5-modifying-files).
Jump to: [top](#)
@@ -1104,10 +1104,11 @@ modes, it also verifies them after the fact and if they are not correct it is an
If you do need different permissions, then see the
FAQ on "[file permissions](#file_perms)". Also keep in mind
[Rule 4 - Files](next/rules.html#rule-4---files),
[Rule 5 - Integrity](next/rules.html#rule-5---integrity),
[Rule 4 - Required files](next/rules.html#rule4-required-files),
[Rule 5 - Do NOT modify submitted files or filenames or parent
directories](next/rules.html#rule5-modifying-files),
and
[Rule 16 - Anonymous](next/rules.html#rule-16---anonymous).
[Rule 16 - Anonymous judging](next/rules.html#rule16-anonymous-judging).
The `txzchk(1)` tool will also verify file/directory permissions (and many other
things) for you, and so will `chksubmit(1)` (along with other checks on files and
@@ -1122,7 +1123,7 @@ The tarball filename **MUST** pass `fnamchk(1)`; the tool `txzchk(1)`
will run `fnamchk(1)` as part of its algorithm. If you use `mkiocccentry(1)`
there should be no problem but if you were to package things manually it is
possible there could be a problem and this poses a big risk of violating
[Rule 4 - Files](next/rules.html#rule-4---files)
[Rule 4 - Required files](next/rules.html#rule4-required-files)
or
[Rule 17 - Use mkiocccentry](next/rules.html#rule17).
@@ -1134,7 +1135,7 @@ discrepancy as an error and exit with non-zero.
These checks **MUST PASS**. If they do not you stand a significant chance of
having your submission rejected for violating
[Rule 4 - Files](next/rules.html#rule-4---files)
[Rule 4 - Required files](next/rules.html#rule4-required-files)
or
[Rule 17 - Use mkiocccentry](next/rules.html#rule17).
@@ -1177,9 +1178,9 @@ The `mkiocccentry(1)` tool uses the v7 format. For instance you might try:
<hr style="width:50%;text-align:left;margin-left:0">
**IMPORTANT**: where
[Rule 4 - Files](next/rules.html#rule-4---files),
[Rule 4 - Required files](next/rules.html#rule4-required-files),
and
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry).
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry)
and the tools from the latest
release of the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry)
conflict, the [IOCCC judges](judges.html) will use their best judgment which
@@ -1220,7 +1221,7 @@ for help here and also read our
FAQ on "[mkiocccentry repo bugs](#mkiocccentry_bugs)".
At the risk of stating the obvious: submissions that violate
[Rule 4 - Files](next/rules.html#rule-4---files),
[Rule 4 - Required files](next/rules.html#rule4-required-files),
or
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry)
**WILL BE REJECTED**, so **BE SURE** to use the latest release of the
@@ -1911,7 +1912,7 @@ Jump to: [top](#)
<div id="rule_2_broken">
<div id="rule_breaking_entry">
### Q 2.4: How did an entry win the IOCCC that breaks Rule 2 - Size?
### Q 2.4: How did an entry win the IOCCC that breaks Rule 2 - Size restrictions?
</div>
</div>
@@ -2210,7 +2211,7 @@ two JSON files, `.auth.json` and `.info.json` as well as the `prog.c`,
`.info.json` manifest. (Okay there is an option to skip files but this is for
the judges **ONLY**; use of this option to validate your submission puts you at
a great risk of violating
[Rule 4 - Files](next/rules.html#rule-4---files),
[Rule 4 - Required files](next/rules.html#rule4-required-files),
or
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry)!).
@@ -2239,7 +2240,7 @@ FAQ on "[.auth.json](#auth_json)"
and the
FAQ on "[.info.json](#info_json)"
as well as
[Rule 4 - Files](next/rules.html#rule-4---files),
[Rule 4 - Required files](next/rules.html#rule4-required-files),
and
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry)
for more information.
@@ -2517,7 +2518,7 @@ At the risk of stating the obvious, if your `.auth.json` file is invalid JSON or
is reported invalid by `chksubmit(1)`, or if your submission directory is
reported invalid by `chksubmit(1)`, your submission will almost certainly be
rejected for violating the [Rules](next/rules.html) and in particular
[Rule 4 - Files](next/rules.html#rule-4---files),
[Rule 4 - Required files](next/rules.html#rule4-required-files),
and
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry).
@@ -2529,7 +2530,7 @@ out of range (see above for list). Two more examples would be if a field is
missing or if an unknown filed is in the file. In these cases (and any others
that must be established as valid by `chksubmit(1)`) your submission would be
rejected for violating
[Rule 4 - Files](next/rules.html#rule-4---files),
[Rule 4 - Required files](next/rules.html#rule4-required-files),
and
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry)
and in particular
@@ -2706,17 +2707,17 @@ In order of the file's contents we describe each required field, below:
tarball, this will be flaggd.
- `rule_2a_size` (number)
* The size calculated of [Rule 2a Gross Size](next/rules.html#rule-2a-gross-size).
* The size calculated of [Rule 2a - Gross Size](next/rules.html#rule2a-gross-size).
**IMPORTANT:** if this violates [Rule 2a](next/rules.html#rule2a) you stand a great
chance of having your submission rejected for violating the
[Rules](next/rules.html)!
- `rule_2b_size` (number)
* The size calculated of [Rule 2b Next Size](next/rules.html#rule-2b-net-size).
* The size calculated of [Rule 2b - Net Size](next/rules.html#rule2b-net-size).
**IMPORTANT:** if this violates
[Rule 2b Next Size](next/rules.html#rule-2b-net-size)
[Rule 2b Net Size](next/rules.html#rule2b-net-size)
you stand a great
chance of having your submission rejected for violating the
[Rules](next/rules.html)!
@@ -2726,11 +2727,11 @@ In order of the file's contents we describe each required field, below:
- `rule_2a_override` (boolean)
* `true` if user overrides warning of
[Rule 2a Gross Size](next/rules.html#rule-2a-gross-size)
[Rule 2a - Gross Size](next/rules.html#rule2a-gross-size)
violation, else `false`.
**IMPORTANT:** if the
[Rule 2a Gross Size](next/rules.html#rule-2a-gross-size)
[Rule 2a - Gross Size](next/rules.html#rule2a-gross-size)
calculated size is **NOT**
violated but this is `true` then you stand a good chance of having your
submission rejected for violating
@@ -2738,39 +2739,26 @@ In order of the file's contents we describe each required field, below:
- `rule_2a_mismatch` (boolean)
* `true` if
[Rule 2a Gross Size](next/rules.html#rule-2a-gross-size)
[Rule 2a - Gross Size](next/rules.html#rule2a-gross-size)
calculated size is not the
same as the file size.
- `rule_2b_override` (boolean)
* `true` if user overrides warning of
[Rule 2b Next Size](next/rules.html#rule-2b-net-size)
[Rule 2b - Net Size](next/rules.html#rule2b-net-size)
violation, else `false`.
**IMPORTANT:** if the
[Rule 2b Next Size](next/rules.html#rule-2b-net-size)
[Rule 2b - Net Size](next/rules.html#rule2b-net-size)
calculated size is **NOT**
violated but this is `true` then you stand a good chance of having your
submission rejected for violating
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry).
- `highbit_warning` (boolean)
* `true` if `iocccsize` detects a high bit (unescaped octets with the high
bit set - octet value >= 128); see
[Rule 12 - UTF-8](next/rules.html#rule-12---utf-8),
else `false`.
- `nul_warning` (boolean)
* `true` if `iocccsize` detects a NUL character in the `prog.c`, else
`false`.
- `trigraph_warning` (boolean)
* `true` if `iocccsize` detects an unknown or invalid trigraph in
`prog.c`, else `false`.
- `wordbuf_warning` (boolean)
* This is ignored and will be removed for IOCCC29 and beyond.
- `ungetc_warning` (boolean)
* `true` if `prog.c` triggered an `ungetc(3)` error, else `false`.
@@ -7437,29 +7425,6 @@ app from time to time to view IOCCC mastodon updates.
Jump to: [top](#)
<div id="mastodon_notifications">
### Q 10.6.1: How can I get push notifications when the judges post something on mastodon?
</div>
To do this you need to go to the [IOCCC mastodon
account](https://fosstodon.org/@ioccc) with a computer (it is unclear how to do
this with a mobile device, if it is even possible) and then you should see a
bell icon. Make sure it's activated. If you mouse over it when it's not enabled
it should look something like this, assuming of course we follow you! :-) (if
not the message about following each other won't show up):
<img src="png/mastodon-notifications.png"
alt="screenshot of Mastodon push notifications"
width=912 height=556>
It is not yet clear if this only works on desktop/computers or mobile devices
too as it was only just discovered (31 July 2025) but whatever the case we
suggest you do it.
Jump to: [top](#)
<div id="tabstops">
### Q 10.7: How do I set certain tabstops for viewing source code in vi(m)?
</div>
news.html
+2 -2
View File
@@ -747,11 +747,11 @@ as well as a critical fix for installing on BSD based systems.</p>
and compile the <a href="faq.html#mkiocccentry">mkiocccentry tool set</a>. You may also wish to install this code.
See also the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/FAQ.md">mkiocccentry FAQ</a> for more information.</p>
<h2 id="section-17">2024-12-30</h2>
<p>The IOCCC <a href="next/rules.html#rule-12---utf-8">Rule 12 - UTF-8</a> no longer discourages the
<p>The IOCCC <a href="next/rules.html#rule12-utf8">Rule 12 - UTF-8</a> no longer discourages the
use of UTF-8 in C source. Since the days of <code>-std=gnu17</code> compilers,
UTF-8 characters do not impose a compiler problem. The related guideline
states that “Rule 13 no longer discourages the use of UTF-8 +characters in C code”.</p>
<p>The IOCCC <a href="next/rules.html#rule-8---submission">Rule 8 - Submission</a> wording has been fixed. It no longer
<p>The IOCCC <a href="next/rules.html#rule8-submitting-requirements">Rule 8 - Submitting requirements</a> wording has been fixed. It no longer
states that email will be sent. Instead it talks about potential slot comment
modifications as means to tell the submitter that their submission was received.</p>
<p>All of the import IOCCC dates within the <a href="next/rules.html">IOCCC rules</a>
news.md
+2 -2
View File
@@ -406,12 +406,12 @@ See also the [mkiocccentry FAQ](https://github.com/ioccc-src/mkiocccentry/blob/m
## 2024-12-30
The IOCCC [Rule 12 - UTF-8](next/rules.html#rule-12---utf-8) no longer discourages the
The IOCCC [Rule 12 - UTF-8](next/rules.html#rule12-utf8) no longer discourages the
use of UTF-8 in C source. Since the days of `-std=gnu17` compilers,
UTF-8 characters do not impose a compiler problem. The related guideline
states that "Rule 13 no longer discourages the use of UTF-8 +characters in C code".
The IOCCC [Rule 8 - Submission](next/rules.html#rule-8---submission) wording has been fixed. It no longer
The IOCCC [Rule 8 - Submitting requirements](next/rules.html#rule8-submitting-requirements) wording has been fixed. It no longer
states that email will be sent. Instead it talks about potential slot comment
modifications as means to tell the submitter that their submission was received.
next/guidelines.html
+22 -1299
View File
File diff suppressed because it is too large. Load diff
next/guidelines.md
+21 -1671
View File
File diff suppressed because it is too large. Load diff
next/rules.html
+21 -13
View File
@@ -460,9 +460,9 @@ IOCCC in the past.</p>
<p>These rules are a <strong>TENTATIVE proposal</strong> for the next IOCCC
and are <strong>likely be to be updated</strong> before the next IOCCC.</p>
<p>See our
FAQ on “<a href="../faq.html#feedback">rules, guidelines and tools feedback</a>”
FAQ on “<a href="../faq.html#feedback">rules, guidelines, tools feedback</a>”
as well as our
FAQ on “<a href="../faq.html#question">asking questions</a>”
FAQ on “<a href="../faq.html#question">about asking questions</a>”
about these rules. You might also find the FAQ in general useful, especially the
FAQ on “<a href="../quick-start.html#enter">how to enter the IOCCC</a>”.</p>
<p>Watch both <a href="../status.html">the IOCCC status page</a> and the
@@ -503,10 +503,12 @@ of the above <strong>dates and times may change <em>AT ANY TIME</em></strong>!</
<div id="rule2">
<div id="rule2-size-restrictions">
<div id="rule2-size">
<div id="rule-2---size">
<h2 id="rule-2---size-restrictions">Rule 2 - Size restrictions</h2>
</div>
</div>
</div>
</div>
<p><code>Rule 2</code> requires that your submission satisfy <strong>BOTH</strong>
<a href="rules.html#rule2a">Rule 2a (Gross Size)</a>
and
@@ -516,9 +518,11 @@ During development this can be checked using <code>iocccsize(1)</code>:</p>
<p>See the <a href="guidelines.html#guideline-2---size">Guidelines for Rule 2 - Size restrictions</a>.</p>
<div id="rule2a">
<div id="rule2a-gross-size">
<div id="rule-2a-gross-size">
<h3 id="rule-2a---gross-size">Rule 2a - Gross Size</h3>
</div>
</div>
</div>
<p>The overall maximum size of your <code>prog.c</code> program source <strong>MUST NOT</strong>
exceed <strong>4993</strong> bytes.</p>
<p><strong>NOTE</strong>: by default <code>iocccsize</code> will only report the rule 2b size, unless the
@@ -526,9 +530,11 @@ code surpasses the limit.</p>
<p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>.</p>
<div id="rule2b">
<div id="rule2b-net-size">
<div id="rule-2b-net-size">
<h3 id="rule-2b---net-size">Rule 2b - Net Size</h3>
</div>
</div>
</div>
<p>When the filename of your program source (i.e., <code>prog.c</code>) is given as a
command line argument to the latest version of the official IOCCC size
tool (hereby referred to as <code>iocccsize(1)</code>), the value printed <strong>MUST
@@ -615,7 +621,8 @@ a case insensitive filesystem.</p></li>
<p>See the
FAQ on “<a href="../faq.html#file_perms">What permissions may my files be and what if I need different permissions?</a>”.</p>
<p>See the <a href="guidelines.html#mkiocccentry_toolkit">Guidelines on the mkiocccentry toolkit</a>.</p>
<p>See the <a href="guidelines.html#makefile">Guidelines on the Makefile</a>.</p>
<p>See the
FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommendations for a submission Makefile?</a>”.</p>
<div id="rule5">
<div id="rule5-modifying-files">
<h2 id="rule-5---do-not-modify-submitted-files-or-filenames-or-parent-directories">Rule 5 - Do NOT modify submitted files or filenames or parent directories</h2>
@@ -677,9 +684,9 @@ validate your submission.</p>
<p>Do <strong>NOT</strong> register more than one account!</p>
<p>See
<a href="rules.html#rule3-register">Rule 3 - Registering for the IOCCC</a>,
<a href="rules.html#rule15-gnu-makefile">Rule 15 - GNU Makefile compatibility</a>,
<a href="rules.html#rule15-gnu-makefile">Rule 15 - GNU Makefile</a>,
and
<a href="rules.html#rule-17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p>
<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p>
<div id="rule9">
<h2 id="rule-9---no-interactive-compiling-allowed">Rule 9 - No interactive compiling allowed</h2>
</div>
@@ -693,7 +700,7 @@ environment</a>.</p>
the make command.</p>
<p><strong>NOTE</strong>: it is better and more portable to <strong>NOT</strong> modify the <code>${CC}</code> variable
in the Makefile.</p>
<p>See <a href="rules.html#rule-15---building">Rule 15 - GNU Makefile compatibility</a>.</p>
<p>See <a href="rules.html#rule15-gnu-makefile">Rule 15 - GNU Makefile</a>.</p>
<div id="rule10">
<h2 id="rule-10---program-file-permissions">Rule 10 - Program file permissions</h2>
</div>
@@ -750,8 +757,8 @@ be rejected. Please do <strong>NOT</strong> put trailing CTRL+M in <code>prog.c<
or <code>remarks.md</code> files, but instead end lines with Unix newline (line-feed,
CTRL+J, <code>\n</code>).</p>
<p>You are permitted, in order to try and squeeze your <code>prog.c</code> under a
<a href="rules.html#rule-2a-gross-size">Rule 2a Gross Size</a> and/or
<a href="rules.html#rule-2b-net-size">Rule 2b Net Size</a>
<a href="rules.html#rule2a-gross-size">Rule 2a Gross Size</a> and/or
<a href="rules.html#rule2b-net-size">Rule 2b Net Size</a>
limits, to <strong>NOT</strong> end source with a newline. If you
need to do this, please document that in your <code>remarks.md</code> file and if
your compiler complains about this, document this too and update your
@@ -793,8 +800,9 @@ GNU long name options (such as <code>--example</code>) or extensions like <code>
<p>Do <strong>NOT</strong> assume that <code>.</code> (current directory) is in the <code>$PATH</code> environment
variable.</p>
<p>See <a href="rules.html#rule4-required-files">Rule 4 - Required files</a>.</p>
<p>See FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommendations for a submission Makefile?</a>”.</p>
<p>See <a href="guidelines.html#guideline-15---building">Guidelines for Rule 15 - GNU Makefile compatibility</a>.</p>
<p>See
FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommendations for a submission Makefile?</a>”.</p>
<p>See <a href="guidelines.html#guideline-15---building">Guidelines for Rule 15 - GNU Makefile</a>.</p>
<div id="rule16">
<div id="rule16-anonymous-judging">
<h2 id="rule-16---anonymous-judging">Rule 16 - Anonymous judging</h2>
@@ -842,7 +850,7 @@ the IOCCC judges only</strong>”, in their respective man pages.</p>
toolkit</a> command lines that confirm
to the command’s <code>-h</code> “<em>print help message</em>”, again notwithstanding the options
for testing and the IOCCC judges.</p>
<p>The <code>prog.c</code> file <strong>MUST</strong> pass the <a href="rules.html#rule-2---size">Rule 2 - Size</a>
<p>The <code>prog.c</code> file <strong>MUST</strong> pass the <a href="rules.html#rule2-size">Rule 2 - Size</a>
checks performed by <code>iocccsize(1)</code>.</p>
<p>The <code>.auth.json</code> and <code>.info.json</code> files <strong>MUST</strong> be compatible with what
<code>mkiocccentry(1)</code> generates.</p>
@@ -865,14 +873,14 @@ FAQ on “<a href="../faq.html#mkiocccentry">What is the mkiocccentry tool, how
<p>This 19th rule, while prime, is reserved for future abuse 😁.
Additional rules, both humorous and otherwise, may be added
below this rule in future contests.</p>
<p>See <a href="rules.html#rule6-free">Rule 6 - Free Rule</a>.</p>
<p>See <a href="rules.html#rule6-free-rule">Rule 6 - Free Rule</a>.</p>
<h2 id="further-reading">Further Reading</h2>
<p>Please read the <a href="guidelines.html">Guidelines</a> next for further commentary on these rules.</p>
<p>Read the
<a href="https://www.ioccc.org/quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>
for an overview of how to enter the contest.</p>
<p>See also the <a href="../faq.html">FAQ</a>.</p>
<p>And now <a href="guidelines.html#fun">for something completely different</a></p>
<p>And now <a href="guidelines.html#fun">for something completely different</a>.</p>
<p>Consider joining the <a href="https://discord.com/invite/Wa42Qujwnw">IOCCC Discord Server</a>
for discussions about The Rules, questions for the Judges, and <code>C</code> in general.</p>
<p>Leonid A. Broukhis
next/rules.md
+21 -13
View File
@@ -10,9 +10,9 @@ These rules are a **TENTATIVE proposal** for the next IOCCC
and are **likely be to be updated** before the next IOCCC.
See our
FAQ on "[rules, guidelines and tools feedback](../faq.html#feedback)"
FAQ on "[rules, guidelines, tools feedback](../faq.html#feedback)"
as well as our
FAQ on "[asking questions](../faq.html#question)"
FAQ on "[about asking questions](../faq.html#question)"
about these rules. You might also find the FAQ in general useful, especially the
FAQ on "[how to enter the IOCCC](../quick-start.html#enter)".
@@ -78,10 +78,12 @@ Your submission **MUST** be a C program that does NOT `#include` data files.
<div id="rule2">
<div id="rule2-size-restrictions">
<div id="rule2-size">
<div id="rule-2---size">
## Rule 2 - Size restrictions
</div>
</div>
</div>
</div>
`Rule 2` requires that your submission satisfy **BOTH**
[Rule 2a &lpar;Gross Size&rpar;](rules.html#rule2a)
@@ -98,9 +100,11 @@ See the [Guidelines for Rule 2 - Size restrictions](guidelines.html#guideline-2-
<div id="rule2a">
<div id="rule2a-gross-size">
<div id="rule-2a-gross-size">
### Rule 2a - Gross Size
</div>
</div>
</div>
The overall maximum size of your `prog.c` program source **MUST NOT**
exceed **4993** bytes.
@@ -113,9 +117,11 @@ See [Entering the IOCCC: the bare minimum you need to know](../quick-start.html#
<div id="rule2b">
<div id="rule2b-net-size">
<div id="rule-2b-net-size">
### Rule 2b - Net Size
</div>
</div>
</div>
When the filename of your program source (i.e., `prog.c`) is given as a
command line argument to the latest version of the official IOCCC size
@@ -234,7 +240,8 @@ FAQ on "[What permissions may my files be and what if I need different permissio
See the [Guidelines on the mkiocccentry toolkit](guidelines.html#mkiocccentry_toolkit).
See the [Guidelines on the Makefile](guidelines.html#makefile).
See the
FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)".
<div id="rule5">
@@ -321,9 +328,9 @@ Do **NOT** register more than one account!
See
[Rule 3 - Registering for the IOCCC](rules.html#rule3-register),
[Rule 15 - GNU Makefile compatibility](rules.html#rule15-gnu-makefile),
[Rule 15 - GNU Makefile](rules.html#rule15-gnu-makefile),
and
[Rule 17 - Use mkiocccentry](rules.html#rule-17-mkiocccentry).
[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry).
<div id="rule9">
@@ -344,7 +351,7 @@ the make command.
**NOTE**: it is better and more portable to **NOT** modify the `${CC}` variable
in the Makefile.
See [Rule 15 - GNU Makefile compatibility](rules.html#rule-15---building).
See [Rule 15 - GNU Makefile](rules.html#rule15-gnu-makefile).
<div id="rule10">
@@ -420,8 +427,8 @@ or `remarks.md` files, but instead end lines with Unix newline (line-feed,
CTRL+J, `\n`).
You are permitted, in order to try and squeeze your `prog.c` under a
[Rule 2a Gross Size](rules.html#rule-2a-gross-size) and/or
[Rule 2b Net Size](rules.html#rule-2b-net-size)
[Rule 2a Gross Size](rules.html#rule2a-gross-size) and/or
[Rule 2b Net Size](rules.html#rule2b-net-size)
limits, to **NOT** end source with a newline. If you
need to do this, please document that in your `remarks.md` file and if
your compiler complains about this, document this too and update your
@@ -480,9 +487,10 @@ variable.
See [Rule 4 - Required files](rules.html#rule4-required-files).
See FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)".
See
FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)".
See [Guidelines for Rule 15 - GNU Makefile compatibility](guidelines.html#guideline-15---building).
See [Guidelines for Rule 15 - GNU Makefile](guidelines.html#guideline-15---building).
<div id="rule16">
@@ -549,7 +557,7 @@ toolkit](https://github.com/ioccc-src/mkiocccentry) command lines that confirm
to the command's `-h` "_print help message_", again notwithstanding the options
for testing and the IOCCC judges.
The `prog.c` file **MUST** pass the [Rule 2 - Size](rules.html#rule-2---size)
The `prog.c` file **MUST** pass the [Rule 2 - Size](rules.html#rule2-size)
checks performed by `iocccsize(1)`.
The `.auth.json` and `.info.json` files **MUST** be compatible with what
@@ -586,7 +594,7 @@ This 19th rule, while prime, is reserved for future abuse 😁.
Additional rules, both humorous and otherwise, may be added
below this rule in future contests.
See [Rule 6 - Free Rule](rules.html#rule6-free).
See [Rule 6 - Free Rule](rules.html#rule6-free-rule).
## Further Reading
@@ -599,7 +607,7 @@ for an overview of how to enter the contest.
See also the [FAQ](../faq.html).
And now [for something completely different](guidelines.html#fun)
And now [for something completely different](guidelines.html#fun).
Consider joining the [IOCCC Discord Server](https://discord.com/invite/Wa42Qujwnw)
for discussions about The Rules, questions for the Judges, and `C` in general.
next/submit.html
+4 -4
View File
@@ -452,7 +452,7 @@
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- BEFORE: 1st line of markdown file: next/submit.md -->
<p>Use mkiocccentry to rebuild# How to upload your submission to the IOCCC</p>
<h1 id="how-to-upload-your-submission-to-the-ioccc">How to upload your submission to the IOCCC</h1>
<p><strong>IMPORTANT NOTE</strong>: The <a href="https://submit.ioccc.org">IOCCC submit server</a>
is only ready for submissions
<strong>ONLY WHEN THE CONTEST IS <a href="../faq.html#open">open</a></strong>.</p>
@@ -518,7 +518,7 @@ the file selection step.</p>
<li>the status of the submission</li>
<li>the filename, which will be in the correct format, assuming you used
<code>mkiocccentry(1)</code> which is <strong>HIGHLY</strong> recommended so that you do not break
<a href="rules.html#rule-17---packaging">Rule 17 - Packaging</a>!</li>
<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>!</li>
<li>the file length, which <code>txzchk(1)</code> will also verify (the file itself and the
tarball listing).</li>
<li>the upload date.</li>
@@ -576,7 +576,7 @@ To see any status updates, you should logout and log back in later.</p>
<p>… or <strong>ANY</strong> other error then you <strong>MUST FIX</strong> your submission, repackage your
tarball with <code>mkiocccentry</code> and upload to the same slot again! If you do not fix
this your submission <strong>WILL BE REJECTED</strong> for violating
<a href="rules.html#rule-17---packaging">Rule 17 - Packaging</a>!</p>
<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>!</p>
<p>If the format test went well, then you will see:</p>
<blockquote>
<p><strong>Status: submit file received by the IOCCC judges. Passed both txzchk and chksubmit tests.</strong></p>
@@ -586,7 +586,7 @@ rules or that everything is OK once the tarball is extracted; it simply means
the tests performed by the tools passed. If you find a flaw in a tool and
abuse it and the tests pass then you stand a significant chance of having your
submission rejected for violating
<a href="rules.html#rule-17---packaging">Rule 17 - Packaging</a>,
<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>,
even if the tests passed.</p>
<p>For details on <code>txzchk</code>, see the
FAQ on “<a href="../faq.html#txzchk">txzchk</a>”.</p>
next/submit.md
+4 -4
View File
@@ -1,4 +1,4 @@
Use mkiocccentry to rebuild# How to upload your submission to the IOCCC
# How to upload your submission to the IOCCC
**IMPORTANT NOTE**: The [IOCCC submit server](https://submit.ioccc.org)
is only ready for submissions
@@ -87,7 +87,7 @@ And in the slot it will give you important details like:
- the status of the submission
- the filename, which will be in the correct format, assuming you used
`mkiocccentry(1)` which is **HIGHLY** recommended so that you do not break
[Rule 17 - Packaging](rules.html#rule-17---packaging)!
[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry)!
- the file length, which `txzchk(1)` will also verify (the file itself and the
tarball listing).
- the upload date.
@@ -158,7 +158,7 @@ Or:
... or **ANY** other error then you **MUST FIX** your submission, repackage your
tarball with `mkiocccentry` and upload to the same slot again! If you do not fix
this your submission **WILL BE REJECTED** for violating
[Rule 17 - Packaging](rules.html#rule-17---packaging)!
[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry)!
If the format test went well, then you will see:
@@ -169,7 +169,7 @@ rules or that everything is OK once the tarball is extracted; it simply means
the tests performed by the tools passed. If you find a flaw in a tool and
abuse it and the tests pass then you stand a significant chance of having your
submission rejected for violating
[Rule 17 - Packaging](rules.html#rule-17---packaging),
[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry),
even if the tests passed.
For details on `txzchk`, see the
quick-start.html
+3 -3
View File
@@ -566,13 +566,13 @@ for more info.</p></li>
<p><strong>NOTE</strong>: Please see our <a href="markdown.html">IOCCC markdown guide</a> for <strong>important information</strong> on using markdown in the IOCCC.</p>
<p>If the <code>mkiocccentry</code> tool indicates that there is a problem with your
submission, especially if it identifies a
<a href="next/rules.html#rule-2---size">Rule 2 - Size</a>,
<a href="next/rules.html#rule2-size">Rule 2 - Size restrictions</a>,
or any other <a href="next/rules.html">rule</a>, related problem, you are <strong>strongly</strong> encouraged to revise and
correct your entry and then re-run the <code>mkiocccentry</code> tool.</p>
<p>If you choose to risk violating <a href="next/rules.html">Rules</a>, be sure and explain your reason
for doing so in your <code>remarks.md</code> file.</p>
<p>See also
<a href="next/rules.html#rule-17---packaging">Rule 17 - Packaging</a>!</p>
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>!</p>
<p><strong>IMPORTANT NOTE</strong>: the tools that require other tools, <code>mkiocccentry(1)</code> and
<code>txzchk(1)</code>, will, as of version <code>2.0.2 2025-03-11</code>, search under <code>$PATH</code>. If
you have an earlier version and you have not installed the tools and run the
@@ -581,7 +581,7 @@ tools to set the path to the required tools.</p>
<p>Do remember to make sure you have the latest vers
<code>chksubmit(1)</code>, <code>txzchk(1)</code> and <code>fnamchk(1)</code>. And remember to make sure you have
the latest version so you do not violate
<a href="next/rules.html#rule-17---packaging">Rule 17 - Packaging</a>.
<a href="next/rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.
See the
FAQ on “<a href="faq.html#obtaining_mkiocccentry">obtaining the latest mkiocccentry tools</a>”,
the
quick-start.md
+3 -3
View File
@@ -162,7 +162,7 @@ Three files are required to exist in `topdir`:
If the `mkiocccentry` tool indicates that there is a problem with your
submission, especially if it identifies a
[Rule 2 - Size](next/rules.html#rule-2---size),
[Rule 2 - Size restrictions](next/rules.html#rule2-size),
or any other [rule](next/rules.html), related problem, you are **strongly** encouraged to revise and
correct your entry and then re-run the `mkiocccentry` tool.
@@ -170,7 +170,7 @@ If you choose to risk violating [Rules](next/rules.html), be sure and explain yo
for doing so in your `remarks.md` file.
See also
[Rule 17 - Packaging](next/rules.html#rule-17---packaging)!
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry)!
**IMPORTANT NOTE**: the tools that require other tools, `mkiocccentry(1)` and
`txzchk(1)`, will, as of version `2.0.2 2025-03-11`, search under `$PATH`. If
@@ -181,7 +181,7 @@ tools to set the path to the required tools.
Do remember to make sure you have the latest vers
`chksubmit(1)`, `txzchk(1)` and `fnamchk(1)`. And remember to make sure you have
the latest version so you do not violate
[Rule 17 - Packaging](next/rules.html#rule-17---packaging).
[Rule 17 - Use mkiocccentry](next/rules.html#rule17-mkiocccentry).
See the
FAQ on "[obtaining the latest mkiocccentry tools](faq.html#obtaining_mkiocccentry)",
the