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

Final fixes for IOCCC guidelines/rules

Browse Source 
Fixed broken links.

Restored text that was accidentally removed during the emergency
recovery of guidelines some days back.

Moved some text that was in the wrong place.

The formatting of the markdown files was changed for shorter lines (for
those viewing the markdown in a viewer rather than a web browser).

Added a <div id> to 2024/index.html so the guidelines (or maybe rules)
could link to the important note from the judges in IOCCC28.

Restore rewording of rule 2b done by @SirWumpus.
This commit is contained in:
Cody Boone Ferguson committed 2025-12-02 05:45:34 -08:00
1 parent 21138c26ce
commit 94f96d7ef9
6 files changed
+2105 -1667
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2024/README.md
+2
View File
@@ -73,7 +73,9 @@ submitting to the IOCCC have become more adept in obfuscation and have
become more skilled in the programming in the C language.
<div id="rule2">
### Code size and Rule 2
</div>
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
2024/index.html
+2
View File
@@ -510,7 +510,9 @@ eclipsing the record of 15 winners!</p>
people extra time to improve their submissions, we also believe that people
submitting to the IOCCC have become more adept in obfuscation and have
become more skilled in the programming in the C language.</p>
<div id="rule2">
<h3 id="code-size-and-rule-2">Code size and Rule 2</h3>
</div>
<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="rules.html#rule2">Rule 2</a> including a fair number of quality
next/guidelines.html
+756 -613
View File
File diff suppressed because it is too large. Load diff
next/guidelines.md
+772 -615
View File
File diff suppressed because it is too large. Load diff
next/rules.html
+281 -216
View File
@@ -455,22 +455,23 @@
<!-- START: this line starts content from: inc/rules.closed.hdr -->
<h1 id="the-ioccc-is-closed">The IOCCC is closed</h1>
<p>The IOCCC is <strong>NOT</strong> accepting new submissions at this time. See the
<a href="../years.html">IOCCC winning entries page</a> for the entries that have won the
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>
<a href="../years.html">IOCCC winning entries page</a> for the entries that have
won the 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, tools feedback</a>”
as well as our
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
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
<a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span> mastodon feed</a> for information about
<p>Watch both <a href="../status.html">the IOCCC status page</a> and the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span>
mastodon feed</a> for information about
future IOCCC openings.</p>
<p><strong>HINT to mastodon users</strong>: You may wish to refresh the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span>
mastodon feed</a> page and/or mastodon
app from time to time to view IOCCC mastodon updates.</p>
mastodon feed</a> page and/or mastodon app
from time to time to view IOCCC mastodon updates.</p>
<!-- END: the next line ends content from: inc/rules.closed.hdr -->
<!-- This is the last line modified by the tool: bin/gen-status.sh -->
<h1 id="th-international-obfuscated-c-code-contest-official-rules">29th International Obfuscated C Code Contest Official Rules</h1>
@@ -480,12 +481,14 @@ granted provided this copyright and notice are included in its entirety
and remains unaltered. All other uses <strong>MUST</strong> receive prior permission in
writing by <a href="../contact.html">contacting the judges</a>.</p>
<h2 id="rules-version">Rules Version</h2>
<p>These IOCCC Rules are version <strong>29.13 2025-12-01</strong>.</p>
<p>These IOCCC Rules are version <strong>29.14 2025-12-02</strong>.</p>
<p class="leftbar">
The <span style="font-size:28px;"><b>|</b></span> symbol indicates an <strong>change</strong> from the previous IOCCC.
The <span style="font-size:28px;"><b>|</b></span> symbol
indicates a <strong>change</strong> from the previous IOCCC.
</p>
<p class="leftbar">
Because the <strong>IOCCC29</strong> rules was a substantial rewrite, only <strong>important changes</strong> from <strong>IOCCC28</strong> have been marked.
Because the <strong>IOCCC29</strong> rules was a substantial rewrite, only
<strong>important changes</strong> from <strong>IOCCC28</strong> have been marked.
</p>
<p>Reminder: be SURE to read the <a href="guidelines.html">IOCCC guidelines</a>.</p>
<div id="rule0">
@@ -495,24 +498,30 @@ Because the <strong>IOCCC29</strong> rules was a substantial rewrite, only <stro
This IOCCC runs from <code>2025-12-03 20:25:12.045045 UTC</code> to <code>2026-03-13 17:19:23.293137 UTC</code>.
</p>
<p class="leftbar">
This contest will enter the <a href="../faq.html#pending">pending state</a> on <code>2025-12-03 20:25:12.045045 UTC</code>,
allowing people to <a href="register.html">register for the IOCCC</a>.
This contest will enter the <a href="../faq.html#pending">pending state</a> on
<code>2025-12-03 20:25:12.045045 UTC</code>, allowing people to <a href="register.html">register for the
IOCCC</a>.
</p>
<p class="leftbar">
This contest will enter the <a href="../faq.html#open">open state</a> on <code>2025-12-15 18:21:24.273033 UTC</code>,
allowing people to <a href="submit.html">upload submissions</a>.
This contest will enter the <a href="../faq.html#open">open state</a> on
<code>2025-12-15 18:21:24.273033 UTC</code>, allowing people to <a href="submit.html">upload
submissions</a>.
</p>
<p class="leftbar">
This contest will enter the <a href="../faq.html#judging">judging state</a> on <code>2026-03-13 17:19:23.293137 UTC</code>,
when people will no longer be allowed to upload submissions.
This contest will enter the <a href="../faq.html#judging">judging state</a> on
<code>2026-03-13 17:19:23.293137 UTC</code>, when people will no longer be allowed
to upload submissions.
</p>
<p>The above <strong>dates and times may change <em>AT ANY TIME</em></strong> until the <a href="../status.html">contest status</a> is <strong>open</strong>.</p>
<p>The above <strong>dates and times may change <em>AT ANY TIME</em></strong> until the
<a href="../status.html">contest status</a> is <strong>open</strong>.</p>
<p class="leftbar">
The above timestamps are in “<em>YYYY-MM-DD HH:MM:SS.micros UTC</em>” format.
</p>
<p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>.</p>
<p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to
know</a>.</p>
<p>See
FAQ on “<a href="../faq.html#feedback">How can I comment or make a suggestion on IOCCC rules, guidelines and tools?</a>”.</p>
FAQ on “<a href="../faq.html#feedback">How can I comment or make a suggestion on IOCCC rules,
guidelines and tools?</a>”.</p>
<div id="rule1">
<div id="rule1-c">
<h2 id="rule-1---c-program">Rule 1 - C program</h2>
@@ -521,7 +530,8 @@ FAQ on “<a href="../faq.html#feedback">How can I comment or make a suggestion
<p class="leftbar">
Your submission <strong>MUST</strong> be a C program.
</p>
<p>See the <a href="guidelines.html#guideline1-c">Guidelines for Rule 1 - C program</a>.</p>
<p>See the <a href="guidelines.html#guideline1-c">Guidelines for Rule 1 - C
program</a>.</p>
<div id="rule2">
<div id="rule2-size-restrictions">
<div id="rule2-size">
@@ -529,13 +539,13 @@ Your submission <strong>MUST</strong> be a C program.
</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
<a href="rules.html#rule2b">Rule 2b (Net Size)</a>.
During development this can be checked using <code>iocccsize(1)</code>:</p>
<p><code>Rule 2</code> requires that your submission satisfy <strong>BOTH</strong> <a href="rules.html#rule2a">Rule 2a
(Gross Size)</a> and <a href="rules.html#rule2b">Rule 2b (Net
Size)</a>.</p>
<p>During development this can be checked using <code>iocccsize(1)</code>:</p>
<pre><code> iocccsize prog.c</code></pre>
<p>See the <a href="guidelines.html#guideline2-size">Guidelines for Rule 2 - Size restrictions</a>.</p>
<p>See the <a href="guidelines.html#guideline2-size">Guidelines for Rule 2 - Size
restrictions</a>.</p>
<div id="rule2a">
<div id="rule2a-gross-size">
<h3 id="rule-2a---gross-size">Rule 2a - Gross Size</h3>
@@ -543,17 +553,15 @@ During development this can be checked using <code>iocccsize(1)</code>:</p>
</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>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>.</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">
<h3 id="rule-2b---net-size">Rule 2b - Net Size</h3>
</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
NOT</strong> exceed <strong>2503</strong>.</p>
<p><strong>NOTE</strong>: <code>iocccsize</code> does <strong>NOT</strong> calculate the filename length.</p>
<p>Check your source code using the latest official IOCCC size tool,
<code>iocccsize(1)</code>. The value printed <strong>MUST NOT</strong> exceed <strong>2503</strong>.</p>
<p>See <a href="#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p>
<div id="rule3">
<div id="rule3-register">
@@ -561,107 +569,120 @@ NOT</strong> exceed <strong>2503</strong>.</p>
</div>
</div>
<p>You <strong>MUST</strong> register, using a valid email address, in order to submit
to the IOCCC. You may register while the contest is <strong>pending</strong> or <strong>open</strong>.</p>
to the IOCCC. You may register while the contest is <strong>pending</strong> or
<strong>open</strong>.</p>
<p>A few days after registering, you’ll receive your UUID username and
temporary password, which you <strong>MUST</strong> change within 14 days.</p>
<p>See <a href="register.html">How to register for the IOCCC</a>.</p>
<p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>.</p>
<p>See <a href="guidelines.html#guideline3-register">Guidelines for Rule 3 - Register for the IOCCC</a>.</p>
<p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to
know</a>.</p>
<p>See <a href="guidelines.html#guideline3-register">Guidelines for Rule 3 - Register for the
IOCCC</a>.</p>
<div id="rule4">
<div id="rule4-required-files">
<h2 id="rule-4---required-files">Rule 4 - Required files</h2>
</div>
</div>
<p class="leftbar">
Your submission <strong>MUST</strong> include at least these files: <code>Makefile</code>, <code>prog.c</code>,
<code>remarks.md</code>,<code>.info.json</code>, and <code>.auth.json</code>, the latter two of which are
generated by <code>mkiocccentry(1)</code>. See <a href="#rule17-mkiocccentry">Rule 17 -
Use mkiocccentry</a>.
Your submission <strong>MUST</strong> include at least these files: <code>Makefile</code>,
<code>prog.c</code>, <code>remarks.md</code>,<code>.info.json</code>, and <code>.auth.json</code>, the latter two
of which are generated by <code>mkiocccentry(1)</code>. See <a href="#rule17-mkiocccentry">Rule 17 - Use
mkiocccentry</a>.
</p>
<p class="leftbar">
At a <strong>minimum</strong> the following requirements apply. Additional requirements
may be imposed by <code>mkiocccentry(1)</code> updates that have yet to be listed
below:
At a <strong>minimum</strong> the following requirements apply. Additional
requirements may be imposed by <code>mkiocccentry(1)</code> updates that have yet
to be listed below:
</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* <code>.info.json</code> and <code>.auth.json</code> <strong>MUST</strong> be generated by <code>mkiocccenty(1)</code>
when packing a submission. When <code>chksubmit(1)</code> is run on the submission
directory <strong>ALL</strong> tests must pass and if there is <strong>ANY</strong> problem with these
JSON files or if either is missing it will fail. See <a href="#rule17-mkiocccentry">Rule 17 - use
mkiocccentry</a>.</p>
* <code>.info.json</code> and <code>.auth.json</code> <strong>MUST</strong> be generated by
<code>mkiocccenty(1)</code> when packing a submission. When <code>chksubmit(1)</code> is run
on the submission directory <strong>ALL</strong> tests must pass and if there is
<strong>ANY</strong> problem with these JSON files or if either is missing it will
fail. See <a href="#rule17-mkiocccentry">Rule 17 - use mkiocccentry</a>.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* The <code>Makefile</code>, <code>remarks.md</code>,<code>.info.json</code>, and <code>.auth.json</code> <strong>MUST</strong>
have a file size <strong>greater than 0</strong> and <strong>MUST</strong> have content. Note that
<code>mkiocccentry(1)</code> will check for file <strong>size</strong> but will <strong>NOT</strong> check for
content.</p>
have a file size <strong>greater than 0</strong> and <strong>MUST</strong> have content. Note
that <code>mkiocccentry(1)</code> will check for file <strong>size</strong> but will <strong>NOT</strong>
check for content.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* Your submitted source code <strong>MUST</strong> be called <code>prog.c</code>. When the <code>Makefile</code>
compiles your code, the executable (if applicable) <strong>MUST</strong> be called <code>prog</code>.
The <code>Makefile</code> may compile your source code into other filenames as well, if you want.</p>
* Your submitted source code <strong>MUST</strong> be called <code>prog.c</code>. When the
<code>Makefile</code> compiles your code, the executable (if applicable) <strong>MUST</strong>
be called <code>prog</code>. The <code>Makefile</code> may compile your source code into
other filenames as well, if you want.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* As <code>prog</code>, <code>prog.alt</code>, <code>prog.alt.o</code>, <code>prog.o</code> may be created by your
<code>Makefile</code>, your submission <strong>MUST NOT</strong> include those files in your <strong>top</strong> directory.</p>
<code>Makefile</code>, your submission <strong>MUST NOT</strong> include those files in your
<strong>top</strong> directory.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* Your submission may <strong>NOT</strong> have any file that starts with <code>COPYING</code>,
<code>COPYRIGHT</code>, or <code>LICENSE</code> as those files are reserved by IOCCC.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* Your submission may <strong>NOT</strong> have in the <strong>top</strong> directory: <code>prog.orig.c</code>,
<code>README.md</code> or <code>index.html</code> as those files are reserved by the IOCCC.</p>
* Your submission may <strong>NOT</strong> have in the <strong>top</strong> directory:
<code>prog.orig.c</code>, <code>README.md</code> or <code>index.html</code> as those files are reserved
by the IOCCC.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* Your submission may <strong>NOT</strong> have in the <strong>top</strong> directory any file
that matches a file glob pattern form <code>[0-9][0-9][0-9][0-9]_*.tar.bz2</code>
as those files are reserved by IOCCC.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* Your submission may <strong>ONLY</strong> contain files and directories. Other file
types such as symlinks, sockets etc. are <strong>NOT</strong> allowed.</p>
* Your submission may <strong>ONLY</strong> contain files and directories. Other
file types such as symlinks, sockets etc. are <strong>NOT</strong> allowed.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* <strong>All</strong> directories <strong>MUST</strong> have permission mode of <strong>0755</strong>. All files
<strong>MUST</strong> have the file mode of <strong>0444</strong>, EXCEPT for files that
* <strong>All</strong> directories <strong>MUST</strong> have permission mode of <strong>0755</strong>. All
files <strong>MUST</strong> have the file mode of <strong>0444</strong>, EXCEPT for files that
end in <code>.sh</code> which must have a mode of <strong>0555</strong>.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* All files that end in <code>.md</code> <strong>MUST</strong> be in markdown format.</p>
<p><span style="font-size:28px;"><b>|</b></span>  
* All filenames are treated as case insensitive. For example, <code>REMARKS.MD</code>,
and <code>Remarks.md</code>, and <code>remarks.md</code> are considered by <code>mkiocccenty(1)</code>
to be the <strong>SAME</strong> file. When preparing a submission on a case
sensitive filesystem, ensure that the submission will work on
* All filenames are treated as case insensitive. For example,
<code>REMARKS.MD</code>, and <code>Remarks.md</code>, and <code>remarks.md</code> are considered by
<code>mkiocccenty(1)</code> to be the <strong>SAME</strong> file. When preparing a submission
on a case sensitive filesystem, ensure that the submission will work on
a case insensitive filesystem.</p>
<p class="leftbar">
<strong>NOTE</strong>: by ‘top directory’ we mean the directory with <code>prog.c</code>, <code>Makefile</code>,
<code>remarks.md</code> and the <code>mkiocccentry(1)</code> generated files <code>.auth.json</code> and
<code>.info.json</code> and <strong>NOT</strong> the <code>topdir</code> arg to <code>mkiocccentry(1)</code>.
<strong>NOTE</strong>: by ‘top directory’ we mean the directory with <code>prog.c</code>,
<code>Makefile</code>, <code>remarks.md</code> and the <code>mkiocccentry(1)</code> generated files
<code>.auth.json</code> and <code>.info.json</code> and <strong>NOT</strong> the <code>topdir</code> arg to
<code>mkiocccentry(1)</code>.
</p>
<p class="leftbar">
<strong>NOTE</strong>: <code>mkiocccentry(1)</code> will reject any directory which has prohibited files.
<strong>NOTE</strong>: <code>mkiocccentry(1)</code> will reject any directory which has
prohibited files.
</p>
<p>The <code>remarks.md</code> and <code>Makefile</code> are explained in more detail in the Guidelines.</p>
<p>The <code>remarks.md</code> and <code>Makefile</code> are explained in more detail in the
<a href="guidelines.html">Guidelines</a>.</p>
<p>See <a href="../markdown.html">IOCCC markdown guidelines</a>.</p>
<p>See <a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p>
<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>
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
FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommendations for a submission Makefile?</a>”.</p>
<p>See the <a href="guidelines.html#mkiocccentry_toolkit">Guidelines on the mkiocccentry toolkit</a>.</p>
FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommendations for a submission
Makefile?</a>”.</p>
<p>See the <a href="guidelines.html#mkiocccentry_toolkit">Guidelines on the mkiocccentry
toolkit</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>
<h2 id="rule-5---do-not-modify-submitted-files-filenames-or-parent-directories">Rule 5 - Do NOT modify submitted files, filenames or parent directories</h2>
</div>
</div>
<p>Your submission <strong>MUST NOT</strong> modify the filenames or content of any of your
original submission, such as <code>prog.c</code>, <code>Makefile</code>, or <strong>ANY</strong> other supplied
files. To modify files, your program can make a copy or you can use the
<code>Makefile</code> to setup working copies. Any working copies <strong>MUST</strong> be cleaned up
by the <code>Makefile</code> <code>clobber</code> target, so as to restore the directory to its
original state.</p>
<p>Your submission <strong>MUST NOT</strong> create or modify directories and files
ABOVE the current directory (with the exception of the <code>/tmp</code> and the <code>/var/tmp</code>
directories and as long as the directory name or filename does <strong>NOT</strong> start
with a <code>.</code> (dot)).</p>
<p>Your submission <strong>MUST NOT</strong> modify the filenames or content of any of
your original submission, such as <code>prog.c</code>, <code>Makefile</code>, or <strong>ANY</strong>
other supplied files. To modify files, your program can make a copy or
you can use the <code>Makefile</code> to setup working copies. Any working copies
<strong>MUST</strong> be cleaned up by the <code>Makefile</code> <code>clobber</code> target, so as to
restore the directory to its original state.</p>
<p>With the exception of the <code>/tmp</code> and the <code>/var/tmp</code> directories,
assuming the directory name or filename does <strong>NOT</strong> start with a <code>.</code>
(dot), your submission <strong>MUST NOT</strong> create or modify directories and
files ABOVE the current directory.</p>
<p>The <code>Makefile</code> <code>clobber</code> target <strong>MUST</strong> restore your submission to its
original form, including the removal of any created files and directories.</p>
original form, including the removal of any created files and
directories.</p>
<p class="leftbar">
Your code should be able to run under a
<a href="https://pubs.opengroup.org/onlinepubs/9799919799/">SUS environment</a>.
Your code should be able to run under a <a href="https://pubs.opengroup.org/onlinepubs/9799919799/">SUS
environment</a>.
</p>
<div id="rule6">
<div id="rule6-free-rule">
@@ -679,72 +700,88 @@ Your code should be able to run under a
</div>
</div>
<p class="leftbar">
You, the author(s), <strong>MUST</strong> own the contents of your submission, <strong>OR</strong>, IF you
do <strong>NOT</strong> own the work, then you <strong>MUST</strong> have permission from the original
owner(s) to its use. If you submit <strong>ANY</strong> content that is owned by others, you
<strong>MUST</strong> detail that ownership, i.e., who owns what, and document the permission
you obtained from them in your <code>remarks.md</code> file.
You, the author(s), <strong>MUST</strong> own the contents of your submission,
<strong>OR</strong>, IF you do <strong>NOT</strong> own the work, then you <strong>MUST</strong> have
permission from the original owner(s) to its use. If you submit
<strong>ANY</strong> content that is owned by others, you <strong>MUST</strong> detail that
ownership, i.e., who owns what, and document the permission you
obtained from them in your <code>remarks.md</code> file.
</p>
<p class="leftbar">
You are permitted to use tools to write your code.
</p>
<p>See <a href="rules.html#rule16-anonymous-judging">Rule 16 - Anonymous Judging</a>,
and
<a href="guidelines.html#guideline7-original">Guidelines for Rule 7 - Original Work</a>.</p>
<a href="guidelines.html#guideline7-original">Guidelines for Rule 7 - Original
Work</a>.</p>
<div id="rule8">
<div id="rule8-submitting-requirements">
<h2 id="rule-8---submitting-requirements">Rule 8 - Submitting requirements</h2>
</div>
</div>
<p>The submit server will accept submissions <strong>ONLY</strong> from those who have
registered and <strong>ONLY</strong> while the contest is open.</p>
<p>The submit server places a total size limit of <strong>3999971</strong> bytes <strong>PER</strong>
submission.</p>
registered and <strong>ONLY</strong> while the contest is open and <strong>ONLY</strong> after
you have changed your initial password.</p>
<p>The submit server places a total size limit of <strong>3999971</strong> bytes
<strong>PER</strong> submission.</p>
<p class="leftbar">
Each account has ten (<strong>10.000</strong>) submission slots (<strong>0..9)</strong>. Each submission
slot should be annotated by the server as to whether its was received,
processed, malformed, etc. Please take note of any errors, rectify,
and resubmit. In order to avoid potential packaging errors, it is <strong>highly
recommended</strong> to use <code>mkiocccentry(1)</code>, <strong>AND</strong> to check from time to time the
status on the submit server, to see if any tests run by the server failed to
validate your submission.
Each account has ten (<strong>10.000</strong>) submission slots (<strong>0..9)</strong>.
</p>
<p class="leftbar">
Each submission slot should be annotated by the server as to whether it
was received, processed, malformed, etc. Please take note of any
errors, rectify, and resubmit.
</p>
<p class="leftbar">
In order to avoid potential packaging errors, it is <strong>highly
recommended</strong> to use <code>mkiocccentry(1)</code>, <strong>AND</strong> to check from time to
time the status on the submit server, to see if any tests run by the
server failed to validate your submission.
</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</a>,
and
<a href="rules.html#rule17-mkiocccentry">Rule 17 - Use mkiocccentry</a>.</p>
<p>See <a href="guidelines.html#guideline8-submitting">Guidelines for Rule 8 - Submitting requirements</a>.</p>
<p>See <a href="guidelines.html#guideline8-submitting">Guidelines for Rule 8 - Submitting
requirements</a>.</p>
<div id="rule9">
<div id="rule9-no-interactive">
<h2 id="rule-9---no-interactive-compiling-allowed">Rule 9 - No interactive compiling allowed</h2>
</div>
</div>
<p>Entries requiring human interaction to be initially compiled are <strong>NOT</strong>
permitted. However, see the guidelines. Each entry <strong>MUST</strong> automate the
build process using <code>bash</code>, <code>gmake</code>, <code>gcc</code> and/or <code>clang</code> and other commonly
available tools under an <a href="https://pubs.opengroup.org/onlinepubs/9799919799/">SUS
permitted. However, see the <a href="guidelines.html#guideline9-no-interactive">guidelines on rule
9</a> as you
<strong>may</strong> suggest alternative compilation steps to do something fun or
cute.</p>
<p>Each entry <strong>MUST</strong> automate the build process using <code>bash</code>, <code>gmake</code>,
<code>gcc</code> and/or <code>clang</code> and other commonly available tools under an <a href="https://pubs.opengroup.org/onlinepubs/9799919799/">SUS
environment</a>.</p>
<p><strong>NOTE</strong>: The references to <code>gmake(1)</code> can be any GNU Make compatible tool.</p>
<p><strong>NOTE</strong>: it is better to use the <code>${MAKE}</code> variable as then one may override
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><strong>NOTE</strong>: any reference to <code>gmake(1)</code> can be any GNU Make compatible
tool.</p>
<p><strong>NOTE</strong>: it is better to use the <code>${MAKE}</code> variable as then one may
override the <code>make</code> command.</p>
<p><strong>NOTE</strong>: it is better to <strong>NOT</strong> modify <code>${CC}</code> in your Makefile as
this makes your program more portable.</p>
<p>See <a href="rules.html#rule15-gnu-makefile">Rule 15 - GNU Makefile</a>.</p>
<p>See <a href="guidelines.html#guideline9-no-interactive">Guidelines for Rule 9 - No interactive compiling allowed</a>.</p>
<p>See <a href="guidelines.html#guideline9-no-interactive">Guidelines for Rule 9 - No interactive compiling
allowed</a>.</p>
<div id="rule10">
<h2 id="rule-10---program-file-permissions">Rule 10 - Program file permissions</h2>
</div>
<p>Programs that require special privileges (<code>setuid(2)</code>, <code>setgid(2)</code>,
super-user, special owner, special group, etc.) are <strong>HIGHLY DISCOURAGED</strong>.
We do <strong>NOT</strong> guarantee these functions will behave as you expect on our
test platforms. If your program needs special permissions you <strong>MUST</strong>
document this fact and explain why it is needed in your submission’s
<code>remarks.md</code> file, preferably close to the top.</p>
super-user, special owner, special group, etc.) are <strong>HIGHLY
DISCOURAGED</strong>. We do <strong>NOT</strong> guarantee these functions will behave as
you expect on our test platforms.</p>
<p>If your program needs special permissions you <strong>MUST</strong> document this
fact and explain why it is needed in your submission’s <code>remarks.md</code>
file, preferably close to the top, because <code>mkiocccentry(1)</code> will
<strong>NOT</strong> set those modes.</p>
<p>Furthermore, if you need a supplementary program that you include to
have these permissions, you will also have to explain this as well, because these
bits are <strong>NOT</strong> allowed in submissions and those bits will <strong>NOT</strong> be copied by
<code>mkiocccentry(1)</code>.</p>
have these permissions, you will also have to explain this as well,
because these bits are <strong>NOT</strong> allowed in submissions and those bits
will <strong>NOT</strong> be copied by <code>mkiocccentry(1)</code> either.</p>
<p>See <a href="rules.html#rule4-required-files">Rule 4 - Required files</a>,
and
<a href="rules.html#rule5-modifying-files">Rule 5 - Do NOT modify files</a>.</p>
@@ -753,95 +790,111 @@ and
<h2 id="rule-11---legal-rule-abuse">Rule 11 - Legal rule abuse</h2>
</div>
</div>
<p>Legal abuse of the rules is <strong>somewhat</strong> encouraged, but comes with risks.
A submission that, in the opinion of the Judges, <strong>violates</strong> the rules <strong>WILL
BE DISQUALIFIED</strong>. Submissions that plan to abuse the rules <strong>MUST</strong> justify
why their rule abuse is legal (or interesting) in the <code>remarks.md</code> file.</p>
<p>Legal abuse of the rules is <strong>somewhat</strong> encouraged, but comes with
risks. A submission that, in the opinion of the Judges, <strong>violates</strong>
the rules <strong>WILL BE DISQUALIFIED</strong>. Submissions that plan to abuse the
rules <strong>MUST</strong> justify why their rule abuse is legal (or interesting)
in the <code>remarks.md</code> file.</p>
<p>Submission packaging abuse will <strong>NOT</strong> be tolerated and for this reason,
amongst many others, it is recommended that you use <code>mkiocccentry(1)</code>. During
development you can check your <code>prog.c</code> size limits using <code>iocccsize(1)</code>, e.g.,
<code>iocccsize -v1 prog.c</code>. Overriding problems detected by any of the IOCCC tools
risks that the submission will be rejected.</p>
amongst many other reasons, it is recommended that you use
<code>mkiocccentry(1)</code>. See also <a href="#rule17-mkiocccentry">Rule 17 - use
mkiocccentry</a>.</p>
<p>During development you can check your <code>prog.c</code> size limits using
<code>iocccsize(1)</code>, e.g., <code>iocccsize -v1 prog.c</code>. Overriding problems
detected by any of the IOCCC tools risks that the submission will be
rejected.</p>
<p>If you do submit a rule abusing or violating submission, then consider
also submitting an alternate version in a different submission server
slot that does <strong>NOT</strong> violate the rules in case your rule abuse excuse
is rejected.</p>
<p><strong>IMPORTANT</strong>: If you do submit such an alternate non-rule abusing
version, <strong>PLEASE</strong> indicate that in your <code>remarks.md</code> file of your non-rule
abusing version so that the Judges don’t think you uploaded a duplicate into a
wrong slot by mistake.</p>
<p>See <a href="guidelines.html#guideline11-abuse">Guidelines for Rule 11 - Legal rule abuse</a>.</p>
version, <strong>PLEASE</strong> indicate that in your <code>remarks.md</code> file of your
non-rule abusing version so that the Judges don’t think you uploaded a
duplicate into a wrong slot by mistake.</p>
<p>See <a href="guidelines.html#guideline11-abuse">Guidelines for Rule 11 - Legal rule
abuse</a>.</p>
<div id="rule12">
<div id="rule12-utf8">
<h2 id="rule-12---utf-8">Rule 12 - UTF-8</h2>
</div>
</div>
<p>Use of UTF-8 is supported by <code>C89</code> standard and its updates and so too by the
IOCCC.</p>
<p>Use of UTF-8 is supported by <code>C89</code> standard and its updates and so too
by the IOCCC.</p>
<p>See <a href="guidelines.html#guideline12-utf8">Guidelines for Rule 12 - UTF-8</a>.</p>
<div id="rule13">
<div id="rule13-nocr">
<h2 id="rule-13---no-carriage-returns-in-prog.c">Rule 13 - No carriage returns in prog.c</h2>
</div>
</div>
<p>Any C source that fails to compile because lines contain carriage-returns
(CTRL+M, <code>\r</code>) in particular as part of DOS/Windows style newlines might
be rejected. Please do <strong>NOT</strong> put trailing CTRL+M in <code>prog.c</code>, <code>Makefile</code>,
or <code>remarks.md</code> files, but instead end lines with Unix newline (line-feed,
CTRL+J, <code>\n</code>).</p>
<p>Any C source that fails to compile because lines contain
carriage-returns (CTRL+M, <code>\r</code>) in particular as part of DOS/Windows
style newlines might be rejected. Please do <strong>NOT</strong> put trailing
CTRL+M in <code>prog.c</code>, <code>Makefile</code>, 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#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
<code>Makefile</code> to account for this.</p>
<p>See <a href="guidelines.html#guideline13-nocr">Guidelines for Rule 13 - No carriage returns in prog.c</a>.</p>
<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 <code>Makefile</code> to account for this.</p>
<p>See <a href="guidelines.html#guideline13-nocr">Guidelines for Rule 13 - No carriage returns in
prog.c</a>.</p>
<div id="rule14">
<h2 id="rule-14---resubmitting-lost-submissions">Rule 14 - Resubmitting lost submissions</h2>
</div>
<p>Submissions that are substantially similar to previous winning IOCCC
entries are discouraged.</p>
<p>You are allowed to resubmit to a later contest, a submission that didn’t win the
IOCCC. If you do so, then you would be <strong>WELL ADVISED</strong> to try and enhance and
improve your submission. If you do resubmit something that didn’t previously
win, then you are encouraged to mention this in your <code>remarks.md</code> file as this
<strong>sometimes</strong> helps.</p>
entries are discouraged. See the
FAQ on “<a href="../faq.html#frequent-themes">What types of entries have been frequently submitted to the
IOCCC?</a>.</p>
<p>You are allowed to resubmit to a later contest, a submission that
didn’t win the IOCCC. If you do so, then you would be <strong>WELL ADVISED</strong>
to try and enhance and improve your submission. If you do resubmit
something that didn’t previously win, then you are encouraged to
mention this in your <code>remarks.md</code> file as this <strong>sometimes</strong> helps.</p>
<div id="rule15">
<div id="rule15-gnu-makefile">
<h2 id="rule-15---gnu-makefile">Rule 15 - GNU Makefile</h2>
</div>
</div>
<p class="leftbar">
The <code>Makefile</code> <strong>MUST</strong> adhere to GNU Makefile syntax. It’s highly recommended
that you copy the <a href="Makefile.example">Makefile.example</a> as a template, renaming
it to <code>Makefile</code>. The primary target of the <code>Makefile</code> <strong>MUST</strong> be <code>prog</code> and
the source file is <code>prog.c</code>. The C compiler and preprocessor <strong>MUST</strong> be
invoked using <code>${CC}</code> and <code>${CPP}</code> macros respectively.
The <code>Makefile</code> <strong>MUST</strong> adhere to GNU Makefile syntax. It’s highly
recommended that you copy the <a href="Makefile.example">Makefile.example</a> as a
template, renaming it to <code>Makefile</code>. The primary target of the
<code>Makefile</code> <strong>MUST</strong> be <code>prog</code> and the source file is <code>prog.c</code>. The C
compiler and preprocessor <strong>MUST</strong> be invoked using <code>${CC}</code> and
<code>${CPP}</code> macros respectively.
</p>
<p>The <code>clobber</code> target <strong>MUST</strong> clean and restore the submission directory tree to
its original state, such as removing temporary files or any modified data files.
Don’t assume that <code>git</code> tool chain is installed, i.e. do <strong>NOT</strong> expect <code>git clean -f</code> to work. To be clear: do <strong>NOT</strong> use <code>git</code> to clean out files as this
can cause problems in the winner repo!</p>
<p>The <code>clobber</code> target <strong>MUST</strong> clean and restore the submission
directory tree to its original state, such as removing temporary files
or any modified data files. Don’t assume that <code>git</code> tool chain is
installed, i.e. do <strong>NOT</strong> expect <code>git clean -f</code> to work. To be clear:
do <strong>NOT</strong> use <code>git</code> to clean out files as this <strong>WILL</strong> cause problems
in the winner repo!</p>
<p class="leftbar">
The <code>Makefile</code> <strong>MUST</strong> use a syntax that is compatible with
<code>bash(1)</code> and GNU <code>make(1)</code>. You are encouraged to use <code>SHELL= bash</code> in your <code>Makefile</code>; please add a space between the <code>=</code> and
the value such as:
The <code>Makefile</code> <strong>MUST</strong> use a syntax that is compatible with <code>bash(1)</code>
and GNU <code>make(1)</code>. You are encouraged to use <code>SHELL= bash</code> in your
<code>Makefile</code>; please add a space between the <code>=</code> and the value such as:
</p>
<pre><code> SHELL= bash</code></pre>
<p class="leftbar">
Assume that commands commonly found in <a href="https://en.wikipedia.org/wiki/Single_UNIX_Specification">Single UNIX
Specification</a>
environments and systems are available in the search
<code>$PATH</code>. Avoid command options that aren’t part of
<code>$PATH</code>.
</p>
<p class="leftbar">
Avoid command options that aren’t part of
<a href="https://en.wikipedia.org/wiki/Single_UNIX_Specification">SUS</a>, such as
GNU long name options (such as <code>--example</code>) or extensions like <code>grep -P</code>.
</p>
<p>Do <strong>NOT</strong> assume that <code>.</code> (current directory) is in the <code>$PATH</code> environment variable.</p>
<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#guideline15-gnu-makefile">Guidelines for Rule 15 - GNU Makefile</a>.</p>
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#guideline15-gnu-makefile">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>
@@ -850,79 +903,88 @@ FAQ on “<a href="../faq.html#makefile_details">What are the detailed recommend
<p>Your source code, data files, remarks, and program output <strong>MUST NOT</strong>
identify the author(s) of your code (unless you are <strong>Peter Honeyman</strong>
or pretending to be <strong>Peter Honeyman</strong>). In order to be impartial the
<a href="https://www.ioccc.org/judges.html">Judges</a> do <strong>NOT</strong> know who is submitting
programs to the IOCCC until final selection is made, and <strong>only</strong> submissions
that won.</p>
<a href="https://www.ioccc.org/judges.html">Judges</a> do <strong>NOT</strong> know who is
submitting programs to the IOCCC until final selection is made, and
<strong>only</strong> submissions that won.</p>
<p>Even if you are a past winner, you <strong>MUST NOT</strong> reveal your identity
deliberately or by accident anywhere in your submission. <strong><em>Failure to comply
may result in the submission being disqualified</em></strong>.</p>
deliberately or by accident anywhere in your submission. <strong><em>Failure to
comply may result in the submission being disqualified</em></strong>.</p>
<div id="rule17">
<div id="rule17-mkiocccentry">
<h2 id="rule-17---use-mkiocccentry">Rule 17 - Use <code>mkiocccentry</code></h2>
</div>
</div>
<p>TL;DR: use <code>mkiocccentry(1)</code> to package your submission.</p>
<p>The files, directories, and paths <strong>MUST</strong> conform to the limits imposed by
<code>mkiocccentry(1)</code>, including but <strong>NOT</strong> limited, to their names, count, path
length, directory tree depth, and permissions.</p>
<p>The files, directories, and paths <strong>MUST</strong> conform to the limits
imposed by <code>mkiocccentry(1)</code>, including but <strong>NOT</strong> limited, to their
names, count, path length, directory tree depth, and permissions.</p>
<p class="leftbar">
The submission tree may have at most <strong>13</strong> directories and maximum
directory depths of <strong>4</strong>. The maximum number of files, excluding
<code>prog.c</code>, <code>remarks.md</code>, <code>Makefile</code>, <code>prog.alt.c</code>, <code>try.sh</code>, <code>try.alt.sh</code>,
<code>.info.json</code> and <code>.auth.json</code> is <strong>31</strong>. And the maximum file-path
component is <strong>38</strong> and maximum path length is <strong>60</strong>.
<code>prog.c</code>, <code>remarks.md</code>, <code>Makefile</code>, <code>prog.alt.c</code>, <code>try.sh</code>,
<code>try.alt.sh</code>, <code>.info.json</code> and <code>.auth.json</code> is <strong>31</strong>. And the maximum
file-path component is <strong>38</strong> and maximum path length is <strong>60</strong>.
</p>
<p>The submission <strong>MUST</strong> be a <code>.txz</code> compressed tarball (i.e., tarball compressed by <code>xz(1)</code>)
as constructed by <code>mkiocccentry(1)</code>, which <strong>MUST</strong> be within <strong>[1..3999971]</strong> bytes in size.</p>
<p>The tarball <strong>MUST</strong> be a <strong>v7 format</strong> tarball, and any supplementary tarballs
you provide <strong>MUST</strong> also be <strong>v7 format</strong>.</p>
<p>The sum of all file lengths, after unpacking from the tarball, <strong>MUST</strong> be
less than <code>27651*1024</code> (<strong>28314624</strong>) bytes.</p>
<p>The submission <strong>MUST</strong> be a <code>.txz</code> compressed tarball (i.e., tarball
compressed by <code>xz(1)</code>) as constructed by <code>mkiocccentry(1)</code>, which
<strong>MUST</strong> be within <strong>[1..3999971]</strong> bytes in size.</p>
<p>The tarball <strong>MUST</strong> be a <strong>v7 format</strong> tarball, and any supplementary
tarballs you provide <strong>MUST</strong> also be <strong>v7 format</strong>.</p>
<p>The sum of all file lengths, after unpacking from the tarball, <strong>MUST</strong>
be less than <code>27651*1024</code> (<strong>28314624</strong>) bytes.</p>
<p class="leftbar">
The submission <strong>MUST</strong> pass all <code>txzchk(1)</code> checks, and the tarball filename
<strong>MUST</strong> pass all <code>fnamchk(1)</code> checks as well.
The submission <strong>MUST</strong> pass all <code>txzchk(1)</code> checks, and the tarball
filename <strong>MUST</strong> pass all <code>fnamchk(1)</code> checks as well.
</p>
<p class="leftbar">
You may <strong>NOT</strong> submit a tarball created by the <code>-d</code>, <code>-e</code> <strong>OR</strong> by the <code>-s seed</code> options of <code>mkiocccentry(1)</code>.
You may <strong>NOT</strong> submit a tarball created by the <code>-d</code>, <code>-e</code> <strong>OR</strong> by
the <code>-s seed</code> options of <code>mkiocccentry(1)</code>.
</p>
<p class="leftbar">
The unpacked submission directory <strong>MUST</strong> pass the checks performed by the
minimum required version of <code>chksubmit(1)</code>.
The unpacked submission directory <strong>MUST</strong> pass the checks performed by
the minimum required version of <code>chksubmit(1)</code>.
</p>
<p class="leftbar">
Submissions may <strong>NOT</strong> use a <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry
toolkit</a> command line options that
are labelled as “<strong>for TESTING purposes</strong>”, <strong>OR</strong> labelled as “<strong>for the use by
the IOCCC judges only</strong>”, in their respective man pages.
toolkit</a> command line
options that are labelled as “<strong>for TESTING purposes</strong>”, <strong>OR</strong>
labelled as “<strong>for the use by the IOCCC judges only</strong>”, in their
respective man pages.
</p>
<p class="leftbar">
Submissions may <strong>ONLY</strong> use <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry
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.
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 class="leftbar">
The <code>prog.c</code> file should pass the <a href="rules.html#rule2-size">Rule 2 - Size restrictions</a>
checks performed by <code>iocccsize(1)</code>.
The <code>prog.c</code> file should pass the <a href="rules.html#rule2-size">Rule 2 - Size
restrictions</a> checks performed by
<code>iocccsize(1)</code>.
</p>
<p class="leftbar">
The <code>.auth.json</code> and <code>.info.json</code> files <strong>MUST</strong> be compatible with what
<code>mkiocccentry(1)</code> generates.
The <code>.auth.json</code> and <code>.info.json</code> files <strong>MUST</strong> be exactly
what the minimum required <code>mkiocccentry(1)</code> version generates.
</p>
<p class="leftbar">
Any submission that fails to pass the checks performed by the minimum required
version of the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry toolkit</a>
<strong>WILL be rejected</strong>!
Any submission that fails to pass the checks performed by the minimum
required version of the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry
toolkit</a> <strong>WILL be
rejected</strong>!
</p>
<p>See <a href="rules.html#rule4-required-files">Rule 4 - Required files</a>.</p>
<p>See the
FAQ on “<a href="../faq.html#mkiocccentry">What is the mkiocccentry tool, how do I obtain it and how do I use it?</a>”.</p>
<p>See the <a href="guidelines.html#guideline17-mkiocccentry">Guidelines for Rule 17 - Use mkiocccentry</a>.</p>
FAQ on “<a href="../faq.html#mkiocccentry">What is the mkiocccentry tool, how do I obtain it and how do I
use it?</a>”.</p>
<p>See the <a href="guidelines.html#guideline17-mkiocccentry">Guidelines for Rule 17 - Use
mkiocccentry</a>.</p>
<div id="rule18">
<h2 id="rule-18---submission-license">Rule 18 - Submission license</h2>
</div>
<p>The entirety of your submission <strong>MUST</strong> be submitted under the following license:</p>
<p><a href="https://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0 International</a></p>
<p>The entirety of your submission <strong>MUST</strong> be submitted under the
following license:</p>
<p><a href="https://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0
International</a>.</p>
<p>See <a href="rules.html#rule7-original-work">Rule 7 - Original Work</a>.</p>
<div id="rule19">
<div id="rule19-prime">
@@ -931,19 +993,22 @@ FAQ on “<a href="../faq.html#mkiocccentry">What is the mkiocccentry tool, how
</div>
<p class="leftbar">
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.
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">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>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>
FAQ on “<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>See also the <a href="../faq.html">FAQ</a> in general.</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>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
chongo (Landon Curt Noll) /\cc/\
<!-- AFTER: last line of markdown file: next/rules.md --></p>
next/rules.md
+292 -223
View File
@@ -3,26 +3,27 @@
# The IOCCC is closed
The IOCCC is **NOT** accepting new submissions at this time. See the
[IOCCC winning entries page](../years.html) for the entries that have won the
IOCCC in the past.
[IOCCC winning entries page](../years.html) for the entries that have
won the IOCCC in the past.
These rules are a **TENTATIVE proposal** for the next IOCCC
and are **likely be to be updated** before the next IOCCC.
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, tools feedback](../faq.html#feedback)"
as well as our
FAQ on "[about asking questions](../faq.html#question)"
about these rules. You might also find the FAQ in general useful, especially the
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)".
Watch both [the IOCCC status page](../status.html) and the
[@IOCCC mastodon feed](https://fosstodon.org/@ioccc) for information about
Watch both [the IOCCC status page](../status.html) and the [@IOCCC
mastodon feed](https://fosstodon.org/@ioccc) for information about
future IOCCC openings.
**HINT to mastodon users**: You may wish to refresh the [@IOCCC
mastodon feed](https://fosstodon.org/@ioccc) page and/or mastodon
app from time to time to view IOCCC mastodon updates.
mastodon feed](https://fosstodon.org/@ioccc) page and/or mastodon app
from time to time to view IOCCC mastodon updates.
<!-- END: the next line ends content from: inc/rules.closed.hdr -->
<!-- This is the last line modified by the tool: bin/gen-status.sh -->
@@ -39,14 +40,16 @@ writing by [contacting the judges](../contact.html).
## Rules Version
These IOCCC Rules are version **29.13 2025-12-01**.
These IOCCC Rules are version **29.14 2025-12-02**.
<p class="leftbar">
The <span style='font-size:28px;'><b>&verbar;</b></span> symbol indicates an **change** from the previous IOCCC.
The <span style='font-size:28px;'><b>&verbar;</b></span> symbol
indicates a **change** from the previous IOCCC.
</p>
<p class="leftbar">
Because the **IOCCC29** rules was a substantial rewrite, only **important changes** from **IOCCC28** have been marked.
Because the **IOCCC29** rules was a substantial rewrite, only
**important changes** from **IOCCC28** have been marked.
</p>
Reminder: be SURE to read the [IOCCC guidelines](guidelines.html).
@@ -57,34 +60,41 @@ Reminder: be SURE to read the [IOCCC guidelines](guidelines.html).
</div>
<p class="leftbar">
This IOCCC runs from `2025-12-03 20:25:12.045045 UTC` to `2026-03-13 17:19:23.293137 UTC`.
This IOCCC runs from `2025-12-03 20:25:12.045045 UTC` to `2026-03-13
17:19:23.293137 UTC`.
</p>
<p class="leftbar">
This contest will enter the [pending state](../faq.html#pending) on `2025-12-03 20:25:12.045045 UTC`,
allowing people to [register for the IOCCC](register.html).
This contest will enter the [pending state](../faq.html#pending) on
`2025-12-03 20:25:12.045045 UTC`, allowing people to [register for the
IOCCC](register.html).
</p>
<p class="leftbar">
This contest will enter the [open state](../faq.html#open) on `2025-12-15 18:21:24.273033 UTC`,
allowing people to [upload submissions](submit.html).
This contest will enter the [open state](../faq.html#open) on
`2025-12-15 18:21:24.273033 UTC`, allowing people to [upload
submissions](submit.html).
</p>
<p class="leftbar">
This contest will enter the [judging state](../faq.html#judging) on `2026-03-13 17:19:23.293137 UTC`,
when people will no longer be allowed to upload submissions.
This contest will enter the [judging state](../faq.html#judging) on
`2026-03-13 17:19:23.293137 UTC`, when people will no longer be allowed
to upload submissions.
</p>
The above **dates and times may change _AT ANY TIME_** until the [contest status](../status.html) is **open**.
The above **dates and times may change _AT ANY TIME_** until the
[contest status](../status.html) is **open**.
<p class="leftbar">
The above timestamps are in "_YYYY-MM-DD HH:MM:SS.micros UTC_" format.
</p>
See [Entering the IOCCC: the bare minimum you need to know](../quick-start.html#enter).
See [Entering the IOCCC: the bare minimum you need to
know](../quick-start.html#enter).
See
FAQ on "[How can I comment or make a suggestion on IOCCC rules, guidelines and tools?](../faq.html#feedback)".
FAQ on "[How can I comment or make a suggestion on IOCCC rules,
guidelines and tools?](../faq.html#feedback)".
<div id="rule1">
@@ -97,7 +107,8 @@ FAQ on "[How can I comment or make a suggestion on IOCCC rules, guidelines and t
Your submission **MUST** be a C program.
</p>
See the [Guidelines for Rule 1 - C program](guidelines.html#guideline1-c).
See the [Guidelines for Rule 1 - C
program](guidelines.html#guideline1-c).
<div id="rule2">
@@ -108,17 +119,18 @@ See the [Guidelines for Rule 1 - C program](guidelines.html#guideline1-c).
</div>
</div>
`Rule 2` requires that your submission satisfy **BOTH**
[Rule 2a &lpar;Gross Size&rpar;](rules.html#rule2a)
and
[Rule 2b &lpar;Net Size&rpar;](rules.html#rule2b).
`Rule 2` requires that your submission satisfy **BOTH** [Rule 2a
&lpar;Gross Size&rpar;](rules.html#rule2a) and [Rule 2b &lpar;Net
Size&rpar;](rules.html#rule2b).
During development this can be checked using `iocccsize(1)`:
``` <!---sh-->
iocccsize prog.c
```
See the [Guidelines for Rule 2 - Size restrictions](guidelines.html#guideline2-size).
See the [Guidelines for Rule 2 - Size
restrictions](guidelines.html#guideline2-size).
<div id="rule2a">
@@ -130,7 +142,8 @@ See the [Guidelines for Rule 2 - Size restrictions](guidelines.html#guideline2-s
The overall maximum size of your `prog.c` program source **MUST NOT**
exceed **4993** bytes.
See [Entering the IOCCC: the bare minimum you need to know](../quick-start.html#enter).
See [Entering the IOCCC: the bare minimum you need to
know](../quick-start.html#enter).
<div id="rule2b">
@@ -139,12 +152,8 @@ See [Entering the IOCCC: the bare minimum you need to know](../quick-start.html#
</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
tool (hereby referred to as `iocccsize(1)`), the value printed **MUST
NOT** exceed **2503**.
**NOTE**: `iocccsize` does **NOT** calculate the filename length.
Check your source code using the latest official IOCCC size tool,
`iocccsize(1)`. The value printed **MUST NOT** exceed **2503**.
See [Rule 17 - Use mkiocccentry](#rule17-mkiocccentry).
@@ -156,16 +165,19 @@ See [Rule 17 - Use mkiocccentry](#rule17-mkiocccentry).
</div>
You **MUST** register, using a valid email address, in order to submit
to the IOCCC. You may register while the contest is **pending** or **open**.
to the IOCCC. You may register while the contest is **pending** or
**open**.
A few days after registering, you'll receive your UUID username and
temporary password, which you **MUST** change within 14 days.
See [How to register for the IOCCC](register.html).
See [Entering the IOCCC: the bare minimum you need to know](../quick-start.html#enter).
See [Entering the IOCCC: the bare minimum you need to
know](../quick-start.html#enter).
See [Guidelines for Rule 3 - Register for the IOCCC](guidelines.html#guideline3-register).
See [Guidelines for Rule 3 - Register for the
IOCCC](guidelines.html#guideline3-register).
<div id="rule4">
@@ -175,47 +187,50 @@ See [Guidelines for Rule 3 - Register for the IOCCC](guidelines.html#guideline3-
</div>
<p class="leftbar">
Your submission **MUST** include at least these files: `Makefile`, `prog.c`,
`remarks.md`,`.info.json`, and `.auth.json`, the latter two of which are
generated by `mkiocccentry(1)`. See [Rule 17 -
Use mkiocccentry](#rule17-mkiocccentry).
Your submission **MUST** include at least these files: `Makefile`,
`prog.c`, `remarks.md`,`.info.json`, and `.auth.json`, the latter two
of which are generated by `mkiocccentry(1)`. See [Rule 17 - Use
mkiocccentry](#rule17-mkiocccentry).
</p>
<p class="leftbar">
At a **minimum** the following requirements apply. Additional requirements
may be imposed by `mkiocccentry(1)` updates that have yet to be listed
below:
At a **minimum** the following requirements apply. Additional
requirements may be imposed by `mkiocccentry(1)` updates that have yet
to be listed below:
</p>
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* `.info.json` and `.auth.json` **MUST** be generated by `mkiocccenty(1)`
when packing a submission. When `chksubmit(1)` is run on the submission
directory **ALL** tests must pass and if there is **ANY** problem with these
JSON files or if either is missing it will fail. See [Rule 17 - use
mkiocccentry](#rule17-mkiocccentry).
* `.info.json` and `.auth.json` **MUST** be generated by
`mkiocccenty(1)` when packing a submission. When `chksubmit(1)` is run
on the submission directory **ALL** tests must pass and if there is
**ANY** problem with these JSON files or if either is missing it will
fail. See [Rule 17 - use mkiocccentry](#rule17-mkiocccentry).
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* The `Makefile`, `remarks.md`,`.info.json`, and `.auth.json` **MUST**
have a file size **greater than 0** and **MUST** have content. Note that
`mkiocccentry(1)` will check for file **size** but will **NOT** check for
content.
have a file size **greater than 0** and **MUST** have content. Note
that `mkiocccentry(1)` will check for file **size** but will **NOT**
check for content.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* Your submitted source code **MUST** be called `prog.c`. When the `Makefile`
compiles your code, the executable (if applicable) **MUST** be called `prog`.
The `Makefile` may compile your source code into other filenames as well, if you want.
* Your submitted source code **MUST** be called `prog.c`. When the
`Makefile` compiles your code, the executable (if applicable) **MUST**
be called `prog`. The `Makefile` may compile your source code into
other filenames as well, if you want.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* As `prog`, `prog.alt`, `prog.alt.o`, `prog.o` may be created by your
`Makefile`, your submission **MUST NOT** include those files in your **top** directory.
`Makefile`, your submission **MUST NOT** include those files in your
**top** directory.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* Your submission may **NOT** have any file that starts with `COPYING`,
`COPYRIGHT`, or `LICENSE` as those files are reserved by IOCCC.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* Your submission may **NOT** have in the **top** directory: `prog.orig.c`,
`README.md` or `index.html` as those files are reserved by the IOCCC.
* Your submission may **NOT** have in the **top** directory:
`prog.orig.c`, `README.md` or `index.html` as those files are reserved
by the IOCCC.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* Your submission may **NOT** have in the **top** directory any file
@@ -223,73 +238,80 @@ that matches a file glob pattern form `[0-9][0-9][0-9][0-9]_*.tar.bz2`
as those files are reserved by IOCCC.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* Your submission may **ONLY** contain files and directories. Other file
types such as symlinks, sockets etc. are **NOT** allowed.
* Your submission may **ONLY** contain files and directories. Other
file types such as symlinks, sockets etc. are **NOT** allowed.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* **All** directories **MUST** have permission mode of **0755**. All files
**MUST** have the file mode of **0444**, EXCEPT for files that
* **All** directories **MUST** have permission mode of **0755**. All
files **MUST** have the file mode of **0444**, EXCEPT for files that
end in `.sh` which must have a mode of **0555**.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* All files that end in `.md` **MUST** be in markdown format.
<span style='font-size:28px;'><b>&verbar;</b></span>&nbsp;&nbsp;
* All filenames are treated as case insensitive. For example, `REMARKS.MD`,
and `Remarks.md`, and `remarks.md` are considered by `mkiocccenty(1)`
to be the **SAME** file. When preparing a submission on a case
sensitive filesystem, ensure that the submission will work on
* All filenames are treated as case insensitive. For example,
`REMARKS.MD`, and `Remarks.md`, and `remarks.md` are considered by
`mkiocccenty(1)` to be the **SAME** file. When preparing a submission
on a case sensitive filesystem, ensure that the submission will work on
a case insensitive filesystem.
<p class="leftbar">
**NOTE**: by 'top directory' we mean the directory with `prog.c`, `Makefile`,
`remarks.md` and the `mkiocccentry(1)` generated files `.auth.json` and
`.info.json` and **NOT** the `topdir` arg to `mkiocccentry(1)`.
**NOTE**: by 'top directory' we mean the directory with `prog.c`,
`Makefile`, `remarks.md` and the `mkiocccentry(1)` generated files
`.auth.json` and `.info.json` and **NOT** the `topdir` arg to
`mkiocccentry(1)`.
</p>
<p class="leftbar">
**NOTE**: `mkiocccentry(1)` will reject any directory which has prohibited files.
**NOTE**: `mkiocccentry(1)` will reject any directory which has
prohibited files.
</p>
The `remarks.md` and `Makefile` are explained in more detail in the Guidelines.
The `remarks.md` and `Makefile` are explained in more detail in the
[Guidelines](guidelines.html).
See [IOCCC markdown guidelines](../markdown.html).
See [Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry).
See the
FAQ on "[What permissions may my files be and what if I need different permissions?](../faq.html#file_perms)".
FAQ on "[What permissions may my files be and what if I need different
permissions?](../faq.html#file_perms)".
See the
FAQ on "[What are the detailed recommendations for a submission Makefile?](../faq.html#makefile_details)".
FAQ on "[What are the detailed recommendations for a submission
Makefile?](../faq.html#makefile_details)".
See the [Guidelines on the mkiocccentry toolkit](guidelines.html#mkiocccentry_toolkit).
See the [Guidelines on the mkiocccentry
toolkit](guidelines.html#mkiocccentry_toolkit).
<div id="rule5">
<div id="rule5-modifying-files">
## Rule 5 - Do NOT modify submitted files or filenames or parent directories
## Rule 5 - Do NOT modify submitted files, filenames or parent directories
</div>
</div>
Your submission **MUST NOT** modify the filenames or content of any of your
original submission, such as `prog.c`, `Makefile`, or **ANY** other supplied
files. To modify files, your program can make a copy or you can use the
`Makefile` to setup working copies. Any working copies **MUST** be cleaned up
by the `Makefile` `clobber` target, so as to restore the directory to its
original state.
Your submission **MUST NOT** modify the filenames or content of any of
your original submission, such as `prog.c`, `Makefile`, or **ANY**
other supplied files. To modify files, your program can make a copy or
you can use the `Makefile` to setup working copies. Any working copies
**MUST** be cleaned up by the `Makefile` `clobber` target, so as to
restore the directory to its original state.
Your submission **MUST NOT** create or modify directories and files
ABOVE the current directory (with the exception of the `/tmp` and the `/var/tmp`
directories and as long as the directory name or filename does **NOT** start
with a `.` (dot)).
With the exception of the `/tmp` and the `/var/tmp` directories,
assuming the directory name or filename does **NOT** start with a `.`
(dot), your submission **MUST NOT** create or modify directories and
files ABOVE the current directory.
The `Makefile` `clobber` target **MUST** restore your submission to its
original form, including the removal of any created files and directories.
original form, including the removal of any created files and
directories.
<p class="leftbar">
Your code should be able to run under a
[SUS environment](https://pubs.opengroup.org/onlinepubs/9799919799/).
Your code should be able to run under a [SUS
environment](https://pubs.opengroup.org/onlinepubs/9799919799/).
</p>
@@ -316,11 +338,12 @@ See [Rule 19 - Prime](rules.html#rule19-prime).
</div>
<p class="leftbar">
You, the author(s), **MUST** own the contents of your submission, **OR**, IF you
do **NOT** own the work, then you **MUST** have permission from the original
owner(s) to its use. If you submit **ANY** content that is owned by others, you
**MUST** detail that ownership, i.e., who owns what, and document the permission
you obtained from them in your `remarks.md` file.
You, the author(s), **MUST** own the contents of your submission,
**OR**, IF you do **NOT** own the work, then you **MUST** have
permission from the original owner(s) to its use. If you submit
**ANY** content that is owned by others, you **MUST** detail that
ownership, i.e., who owns what, and document the permission you
obtained from them in your `remarks.md` file.
</p>
<p class="leftbar">
@@ -329,7 +352,8 @@ You are permitted to use tools to write your code.
See [Rule 16 - Anonymous Judging](rules.html#rule16-anonymous-judging),
and
[Guidelines for Rule 7 - Original Work](guidelines.html#guideline7-original).
[Guidelines for Rule 7 - Original
Work](guidelines.html#guideline7-original).
<div id="rule8">
@@ -339,19 +363,27 @@ and
</div>
The submit server will accept submissions **ONLY** from those who have
registered and **ONLY** while the contest is open.
registered and **ONLY** while the contest is open and **ONLY** after
you have changed your initial password.
The submit server places a total size limit of **3999971** bytes **PER**
submission.
The submit server places a total size limit of **3999971** bytes
**PER** submission.
<p class="leftbar">
Each account has ten (**10.000**) submission slots (**0..9)**. Each submission
slot should be annotated by the server as to whether its was received,
processed, malformed, etc. Please take note of any errors, rectify,
and resubmit. In order to avoid potential packaging errors, it is **highly
recommended** to use `mkiocccentry(1)`, **AND** to check from time to time the
status on the submit server, to see if any tests run by the server failed to
validate your submission.
Each account has ten (**10.000**) submission slots (**0..9)**.
</p>
<p class="leftbar">
Each submission slot should be annotated by the server as to whether it
was received, processed, malformed, etc. Please take note of any
errors, rectify, and resubmit.
</p>
<p class="leftbar">
In order to avoid potential packaging errors, it is **highly
recommended** to use `mkiocccentry(1)`, **AND** to check from time to
time the status on the submit server, to see if any tests run by the
server failed to validate your submission.
</p>
See
@@ -360,7 +392,8 @@ See
and
[Rule 17 - Use mkiocccentry](rules.html#rule17-mkiocccentry).
See [Guidelines for Rule 8 - Submitting requirements](guidelines.html#guideline8-submitting).
See [Guidelines for Rule 8 - Submitting
requirements](guidelines.html#guideline8-submitting).
<div id="rule9">
@@ -370,22 +403,28 @@ See [Guidelines for Rule 8 - Submitting requirements](guidelines.html#guideline8
</div>
Entries requiring human interaction to be initially compiled are **NOT**
permitted. However, see the guidelines. Each entry **MUST** automate the
build process using `bash`, `gmake`, `gcc` and/or `clang` and other commonly
available tools under an [SUS
permitted. However, see the [guidelines on rule
9](guidelines.html#guideline9-no-interactive) as you
**may** suggest alternative compilation steps to do something fun or
cute.
Each entry **MUST** automate the build process using `bash`, `gmake`,
`gcc` and/or `clang` and other commonly available tools under an [SUS
environment](https://pubs.opengroup.org/onlinepubs/9799919799/).
**NOTE**: The references to `gmake(1)` can be any GNU Make compatible tool.
**NOTE**: any reference to `gmake(1)` can be any GNU Make compatible
tool.
**NOTE**: it is better to use the `${MAKE}` variable as then one may override
the make command.
**NOTE**: it is better to use the `${MAKE}` variable as then one may
override the `make` command.
**NOTE**: it is better and more portable to **NOT** modify the `${CC}` variable
in the Makefile.
**NOTE**: it is better to **NOT** modify `${CC}` in your Makefile as
this makes your program more portable.
See [Rule 15 - GNU Makefile](rules.html#rule15-gnu-makefile).
See [Guidelines for Rule 9 - No interactive compiling allowed](guidelines.html#guideline9-no-interactive).
See [Guidelines for Rule 9 - No interactive compiling
allowed](guidelines.html#guideline9-no-interactive).
<div id="rule10">
@@ -393,16 +432,19 @@ See [Guidelines for Rule 9 - No interactive compiling allowed](guidelines.html#g
</div>
Programs that require special privileges (`setuid(2)`, `setgid(2)`,
super-user, special owner, special group, etc.) are **HIGHLY DISCOURAGED**.
We do **NOT** guarantee these functions will behave as you expect on our
test platforms. If your program needs special permissions you **MUST**
document this fact and explain why it is needed in your submission’s
`remarks.md` file, preferably close to the top.
super-user, special owner, special group, etc.) are **HIGHLY
DISCOURAGED**. We do **NOT** guarantee these functions will behave as
you expect on our test platforms.
If your program needs special permissions you **MUST** document this
fact and explain why it is needed in your submission’s `remarks.md`
file, preferably close to the top, because `mkiocccentry(1)` will
**NOT** set those modes.
Furthermore, if you need a supplementary program that you include to
have these permissions, you will also have to explain this as well, because these
bits are **NOT** allowed in submissions and those bits will **NOT** be copied by
`mkiocccentry(1)`.
have these permissions, you will also have to explain this as well,
because these bits are **NOT** allowed in submissions and those bits
will **NOT** be copied by `mkiocccentry(1)` either.
See [Rule 4 - Required files](rules.html#rule4-required-files),
and
@@ -415,16 +457,21 @@ and
</div>
</div>
Legal abuse of the rules is **somewhat** encouraged, but comes with risks.
A submission that, in the opinion of the Judges, **violates** the rules **WILL
BE DISQUALIFIED**. Submissions that plan to abuse the rules **MUST** justify
why their rule abuse is legal (or interesting) in the `remarks.md` file.
Legal abuse of the rules is **somewhat** encouraged, but comes with
risks. A submission that, in the opinion of the Judges, **violates**
the rules **WILL BE DISQUALIFIED**. Submissions that plan to abuse the
rules **MUST** justify why their rule abuse is legal (or interesting)
in the `remarks.md` file.
Submission packaging abuse will **NOT** be tolerated and for this reason,
amongst many others, it is recommended that you use `mkiocccentry(1)`. During
development you can check your `prog.c` size limits using `iocccsize(1)`, e.g.,
`iocccsize -v1 prog.c`. Overriding problems detected by any of the IOCCC tools
risks that the submission will be rejected.
amongst many other reasons, it is recommended that you use
`mkiocccentry(1)`. See also [Rule 17 - use
mkiocccentry](#rule17-mkiocccentry).
During development you can check your `prog.c` size limits using
`iocccsize(1)`, e.g., `iocccsize -v1 prog.c`. Overriding problems
detected by any of the IOCCC tools risks that the submission will be
rejected.
If you do submit a rule abusing or violating submission, then consider
also submitting an alternate version in a different submission server
@@ -432,11 +479,12 @@ slot that does **NOT** violate the rules in case your rule abuse excuse
is rejected.
**IMPORTANT**: If you do submit such an alternate non-rule abusing
version, **PLEASE** indicate that in your `remarks.md` file of your non-rule
abusing version so that the Judges don't think you uploaded a duplicate into a
wrong slot by mistake.
version, **PLEASE** indicate that in your `remarks.md` file of your
non-rule abusing version so that the Judges don't think you uploaded a
duplicate into a wrong slot by mistake.
See [Guidelines for Rule 11 - Legal rule abuse](guidelines.html#guideline11-abuse).
See [Guidelines for Rule 11 - Legal rule
abuse](guidelines.html#guideline11-abuse).
<div id="rule12">
@@ -445,8 +493,8 @@ See [Guidelines for Rule 11 - Legal rule abuse](guidelines.html#guideline11-abus
</div>
</div>
Use of UTF-8 is supported by `C89` standard and its updates and so too by the
IOCCC.
Use of UTF-8 is supported by `C89` standard and its updates and so too
by the IOCCC.
See [Guidelines for Rule 12 - UTF-8](guidelines.html#guideline12-utf8).
@@ -457,21 +505,21 @@ See [Guidelines for Rule 12 - UTF-8](guidelines.html#guideline12-utf8).
</div>
</div>
Any C source that fails to compile because lines contain carriage-returns
(CTRL+M, `\r`) in particular as part of DOS/Windows style newlines might
be rejected. Please do **NOT** put trailing CTRL+M in `prog.c`, `Makefile`,
or `remarks.md` files, but instead end lines with Unix newline (line-feed,
CTRL+J, `\n`).
Any C source that fails to compile because lines contain
carriage-returns (CTRL+M, `\r`) in particular as part of DOS/Windows
style newlines might be rejected. Please do **NOT** put trailing
CTRL+M in `prog.c`, `Makefile`, 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#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
`Makefile` to account for this.
[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 `Makefile` to account for this.
See [Guidelines for Rule 13 - No carriage returns in prog.c](guidelines.html#guideline13-nocr).
See [Guidelines for Rule 13 - No carriage returns in
prog.c](guidelines.html#guideline13-nocr).
<div id="rule14">
@@ -479,14 +527,15 @@ See [Guidelines for Rule 13 - No carriage returns in prog.c](guidelines.html#gui
</div>
Submissions that are substantially similar to previous winning IOCCC
entries are discouraged.
You are allowed to resubmit to a later contest, a submission that didn't win the
IOCCC. If you do so, then you would be **WELL ADVISED** to try and enhance and
improve your submission. If you do resubmit something that didn't previously
win, then you are encouraged to mention this in your `remarks.md` file as this
**sometimes** helps.
entries are discouraged. See the
FAQ on "[What types of entries have been frequently submitted to the
IOCCC?](../faq.html#frequent-themes).
You are allowed to resubmit to a later contest, a submission that
didn't win the IOCCC. If you do so, then you would be **WELL ADVISED**
to try and enhance and improve your submission. If you do resubmit
something that didn't previously win, then you are encouraged to
mention this in your `remarks.md` file as this **sometimes** helps.
<div id="rule15">
<div id="rule15-gnu-makefile">
@@ -495,24 +544,25 @@ win, then you are encouraged to mention this in your `remarks.md` file as this
</div>
<p class="leftbar">
The `Makefile` **MUST** adhere to GNU Makefile syntax. It's highly recommended
that you copy the [Makefile.example](Makefile.example) as a template, renaming
it to `Makefile`. The primary target of the `Makefile` **MUST** be `prog` and
the source file is `prog.c`. The C compiler and preprocessor **MUST** be
invoked using `${CC}` and `${CPP}` macros respectively.
The `Makefile` **MUST** adhere to GNU Makefile syntax. It's highly
recommended that you copy the [Makefile.example](Makefile.example) as a
template, renaming it to `Makefile`. The primary target of the
`Makefile` **MUST** be `prog` and the source file is `prog.c`. The C
compiler and preprocessor **MUST** be invoked using `${CC}` and
`${CPP}` macros respectively.
</p>
The `clobber` target **MUST** clean and restore the submission directory tree to
its original state, such as removing temporary files or any modified data files.
Don't assume that `git` tool chain is installed, i.e. do **NOT** expect `git
clean -f` to work. To be clear: do **NOT** use `git` to clean out files as this
can cause problems in the winner repo!
The `clobber` target **MUST** clean and restore the submission
directory tree to its original state, such as removing temporary files
or any modified data files. Don't assume that `git` tool chain is
installed, i.e. do **NOT** expect `git clean -f` to work. To be clear:
do **NOT** use `git` to clean out files as this **WILL** cause problems
in the winner repo!
<p class="leftbar">
The `Makefile` **MUST** use a syntax that is compatible with
`bash(1)` and GNU `make(1)`. You are encouraged to use `SHELL=
bash` in your `Makefile`; please add a space between the `=` and
the value such as:
The `Makefile` **MUST** use a syntax that is compatible with `bash(1)`
and GNU `make(1)`. You are encouraged to use `SHELL= bash` in your
`Makefile`; please add a space between the `=` and the value such as:
</p>
``` <!---makefile-->
@@ -523,19 +573,27 @@ the value such as:
Assume that commands commonly found in [Single UNIX
Specification](https://en.wikipedia.org/wiki/Single_UNIX_Specification)
environments and systems are available in the search
`$PATH`. Avoid command options that aren't part of
[SUS](https://en.wikipedia.org/wiki/Single_UNIX_Specification), such as
GNU long name options (such as `--example`) or extensions like `grep -P`.
`$PATH`.
</p>
Do **NOT** assume that `.` (current directory) is in the `$PATH` environment variable.
<p class="leftbar">
Avoid command options that aren't part of
[SUS](https://en.wikipedia.org/wiki/Single_UNIX_Specification), such as
GNU long name options (such as `--example`) or extensions like `grep
-P`.
</p>
Do **NOT** assume that `.` (current directory) is in the `$PATH`
environment 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)".
FAQ on "[What are the detailed recommendations for a submission
Makefile?](../faq.html#makefile_details)".
See [Guidelines for Rule 15 - GNU Makefile](guidelines.html#guideline15-gnu-makefile).
See [Guidelines for Rule 15 - GNU
Makefile](guidelines.html#guideline15-gnu-makefile).
<div id="rule16">
@@ -547,13 +605,13 @@ See [Guidelines for Rule 15 - GNU Makefile](guidelines.html#guideline15-gnu-make
Your source code, data files, remarks, and program output **MUST NOT**
identify the author(s) of your code (unless you are **Peter Honeyman**
or pretending to be **Peter Honeyman**). In order to be impartial the
[Judges](https://www.ioccc.org/judges.html) do **NOT** know who is submitting
programs to the IOCCC until final selection is made, and **only** submissions
that won.
[Judges](https://www.ioccc.org/judges.html) do **NOT** know who is
submitting programs to the IOCCC until final selection is made, and
**only** submissions that won.
Even if you are a past winner, you **MUST NOT** reveal your identity
deliberately or by accident anywhere in your submission. **_Failure to comply
may result in the submission being disqualified_**.
deliberately or by accident anywhere in your submission. **_Failure to
comply may result in the submission being disqualified_**.
<div id="rule17">
@@ -564,87 +622,95 @@ may result in the submission being disqualified_**.
TL;DR: use `mkiocccentry(1)` to package your submission.
The files, directories, and paths **MUST** conform to the limits imposed by
`mkiocccentry(1)`, including but **NOT** limited, to their names, count, path
length, directory tree depth, and permissions.
The files, directories, and paths **MUST** conform to the limits
imposed by `mkiocccentry(1)`, including but **NOT** limited, to their
names, count, path length, directory tree depth, and permissions.
<p class="leftbar">
The submission tree may have at most **13** directories and maximum
directory depths of **4**. The maximum number of files, excluding
`prog.c`, `remarks.md`, `Makefile`, `prog.alt.c`, `try.sh`, `try.alt.sh`,
`.info.json` and `.auth.json` is **31**. And the maximum file-path
component is **38** and maximum path length is **60**.
`prog.c`, `remarks.md`, `Makefile`, `prog.alt.c`, `try.sh`,
`try.alt.sh`, `.info.json` and `.auth.json` is **31**. And the maximum
file-path component is **38** and maximum path length is **60**.
</p>
The submission **MUST** be a `.txz` compressed tarball (i.e., tarball compressed by `xz(1)`)
as constructed by `mkiocccentry(1)`, which **MUST** be within **[1..3999971]** bytes in size.
The submission **MUST** be a `.txz` compressed tarball (i.e., tarball
compressed by `xz(1)`) as constructed by `mkiocccentry(1)`, which
**MUST** be within **[1..3999971]** bytes in size.
The tarball **MUST** be a **v7 format** tarball, and any supplementary tarballs
you provide **MUST** also be **v7 format**.
The tarball **MUST** be a **v7 format** tarball, and any supplementary
tarballs you provide **MUST** also be **v7 format**.
The sum of all file lengths, after unpacking from the tarball, **MUST** be
less than `27651*1024` (**28314624**) bytes.
The sum of all file lengths, after unpacking from the tarball, **MUST**
be less than `27651*1024` (**28314624**) bytes.
<p class="leftbar">
The submission **MUST** pass all `txzchk(1)` checks, and the tarball filename
**MUST** pass all `fnamchk(1)` checks as well.
The submission **MUST** pass all `txzchk(1)` checks, and the tarball
filename **MUST** pass all `fnamchk(1)` checks as well.
</p>
<p class="leftbar">
You may **NOT** submit a tarball created by the `-d`, `-e` **OR** by the `-s
seed` options of `mkiocccentry(1)`.
You may **NOT** submit a tarball created by the `-d`, `-e` **OR** by
the `-s seed` options of `mkiocccentry(1)`.
</p>
<p class="leftbar">
The unpacked submission directory **MUST** pass the checks performed by the
minimum required version of `chksubmit(1)`.
The unpacked submission directory **MUST** pass the checks performed by
the minimum required version of `chksubmit(1)`.
</p>
<p class="leftbar">
Submissions may **NOT** use a [mkiocccentry
toolkit](https://github.com/ioccc-src/mkiocccentry) command line options that
are labelled as "**for TESTING purposes**", **OR** labelled as "**for the use by
the IOCCC judges only**", in their respective man pages.
toolkit](https://github.com/ioccc-src/mkiocccentry) command line
options that are labelled as "**for TESTING purposes**", **OR**
labelled as "**for the use by the IOCCC judges only**", in their
respective man pages.
</p>
<p class="leftbar">
Submissions may **ONLY** use [mkiocccentry
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.
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.
</p>
<p class="leftbar">
The `prog.c` file should pass the [Rule 2 - Size restrictions](rules.html#rule2-size)
checks performed by `iocccsize(1)`.
The `prog.c` file should pass the [Rule 2 - Size
restrictions](rules.html#rule2-size) checks performed by
`iocccsize(1)`.
</p>
<p class="leftbar">
The `.auth.json` and `.info.json` files **MUST** be compatible with what
`mkiocccentry(1)` generates.
The `.auth.json` and `.info.json` files **MUST** be exactly
what the minimum required `mkiocccentry(1)` version generates.
</p>
<p class="leftbar">
Any submission that fails to pass the checks performed by the minimum required
version of the [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry)
**WILL be rejected**!
Any submission that fails to pass the checks performed by the minimum
required version of the [mkiocccentry
toolkit](https://github.com/ioccc-src/mkiocccentry) **WILL be
rejected**!
</p>
See [Rule 4 - Required files](rules.html#rule4-required-files).
See the
FAQ on "[What is the mkiocccentry tool, how do I obtain it and how do I use it?](../faq.html#mkiocccentry)".
FAQ on "[What is the mkiocccentry tool, how do I obtain it and how do I
use it?](../faq.html#mkiocccentry)".
See the [Guidelines for Rule 17 - Use mkiocccentry](guidelines.html#guideline17-mkiocccentry).
See the [Guidelines for Rule 17 - Use
mkiocccentry](guidelines.html#guideline17-mkiocccentry).
<div id="rule18">
## Rule 18 - Submission license
</div>
The entirety of your submission **MUST** be submitted under the following license:
The entirety of your submission **MUST** be submitted under the
following license:
[CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/)
[CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0
International](https://creativecommons.org/licenses/by-sa/4.0/).
See [Rule 7 - Original Work](rules.html#rule7-original-work).
@@ -657,8 +723,8 @@ See [Rule 7 - Original Work](rules.html#rule7-original-work).
<p class="leftbar">
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.
Additional rules, both humorous and otherwise, may be added below this
rule in future contests.
</p>
See [Rule 6 - Free Rule](rules.html#rule6-free-rule).
@@ -666,18 +732,21 @@ See [Rule 6 - Free Rule](rules.html#rule6-free-rule).
## Further Reading
Please read the [Guidelines](guidelines.html) next for further commentary on these rules.
Please read the [Guidelines](guidelines.html) next for further
commentary on these rules.
Read the
[Entering the IOCCC: the bare minimum you need to know](https://www.ioccc.org/quick-start.html#enter)
FAQ on "[Entering the IOCCC: the bare minimum you need to
know](https://www.ioccc.org/quick-start.html#enter)"
for an overview of how to enter the contest.
See also the [FAQ](../faq.html).
See also the [FAQ](../faq.html) in general.
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.
Consider joining the [IOCCC Discord
Server](https://discord.com/invite/Wa42Qujwnw) for discussions about
The Rules, questions for the Judges, and `C` in general.
Leonid A. Broukhis
chongo (Landon Curt Noll) /\\cc/\\