The IOCCC is NOT accepting new submissions at this time. See the -IOCCC winning entries page for the entries that have won the -IOCCC in the past.
-These guidelines 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” -as well as our -FAQ on “about asking questions” -about these guidelines. You might also find the FAQ in general useful, especially the -FAQ on “how to enter the IOCCC”.
-Watch both the IOCCC status page and the -@IOCCC mastodon feed for information about -future IOCCC openings.
-HINT to mastodon users: You may wish to refresh the @IOCCC -mastodon feed page and/or mastodon -app from time to time to view IOCCC mastodon updates.
- -All Rights Reserved. Permission for personal, education or non-profit use is -granted provided this this copyright and notice are included in its entirety +granted provided this copyright and notice are included in its entirety and remains unaltered. All other uses must receive prior permission in writing by contacting the judges.
-iocccsize(1) algorithm.
Jump to: top
See FAQ on “What is an author handle?”.
@@ -557,10 +536,10 @@ because of theiocccsize(1) algorithm.
The IOCCC has a rich history of remarkable winning entries created by -authors who skillfully employed various techniques to develop their code.
-If you do make use of such tools or services, then we ENCOURAGE you to describe
-how you used such tools in your remarks.md file.
In short: You created it, you own it, and its an original work, or you have explicit permission.
+authors who skillfully employed various techniques to develop their code. +If you do make use of such tools or services, then we ENCOURAGE you to +describe how you used such tools in yourremarks.md file.
+In short: You created it, you own it, its an original work, or you have explicit permission to the work.
See FAQ on “May I use AI, LLM, Virtual coding assistants, or similar tools to write my submission?”.
Jump to: top
remarks.md file.
We try to avoid limiting creativity in our IOCCC rules so -we leave the contest open for creative rule interpretation.
We do realize that there are holes in the IOCCC rules, and invite -submitters to attempt to exploit them.
+submitters to attempt to apply creative rule interpretation. A rule abuse though, even +if not rewarded, may result in a subsequent rule change for future contests.We sometime award ‘Best abuse of the rules’ or ‘Worst abuse of the rules’, or some variation, to a submission that creatively attempts to exploit a holes in the IOCCC rules.
-When we do need to plug a hole in the IOCCC rules or -IOCCC guidelines, we will attempt to use a very small plug, +
When we do need to plug a hole in the IOCCC rules +or IOCCC guidelines, we will attempt to use a very small plug, if not smaller.
Or, maybe not. :-)
-Legal abuse of the IOCCC rules is somewhat encouraged. Legal rule abuse -may involve, but is not limited to, doing things that are technically allowed by -the IOCCC rules and yet do not fit the spirit of what we intended to be -submitted.
-Legal rule abuse is encouraged to help promote creativity. Rule abuse -submissions, regardless of if they receive an award, result in changes to -the next year’s IOCCC rules and IOCCC guidelines.
-Legal abuse of the IOCCC rules is NOT an invitation to violate the -IOCCC rules. A submission that violates the rules in the -opinion of the IOCCC judges, WILL be -disqualified. RULE ABUSE CARRIES A CERTAIN LEVEL OF RISK! If you -have a submission that might otherwise be interesting, you might want to -submit two versions; one that does not abuse the IOCCC rules and one that -does, making sure to note in the one that does not abuse the rules that this is -another version, so that the judges do not assume you uploaded it by mistake.
+Legal rule abuse may involve, but is not limited to, doing things that are +technically allowed by the IOCCC rules and yet do not fit the spirit of what +we intended to be submitted.
+Legal abuse of the IOCCC rules is NOT an invitation to violate +the IOCCC rules (especailly Rule 17 - +Packaging ). A submission that violates the +rules in the opinion of the IOCCC judges, +WILL be disqualified. RULE ABUSE CARRIES A CERTAIN LEVEL OF RISK!
If you intend to abuse the IOCCC rules,
-indicate so in your remarks.md file. You MUST try to justify
+indicate so in your remarks.md file. You MUST try to justify, plead, beg,
why you consider your rule abuse to be allowed under the
-IOCCC rules. That is, you must plead your case as to why
-your submission is valid. Humor and/or creativity help plead a case.
+IOCCC rules. Humor or creativity help plead a case.
As there is no guarantee that you will succeed, you might consider
submitting an alternate version that conforms to the
IOCCC rules.
If you have a submission that might otherwise be interesting, you might want to +submit two versions; one that does not abuse the IOCCC rules and +one that does, making sure to note in the one that does not abuse the rules that +this is another version, so that the judges do not assume you uploaded it by +mistake.
If you do bypass the mkiocccentry(1) warnings about
Rule 2a - Gross Size
and/or about
@@ -611,14 +586,11 @@ rule and submit a submission anyway, you MUST try to justify wh
IOCCC judges should not reject your submission due to a rule
violation, and you would be wise to do this towards the top of your remarks.md
file.
Abusing the web submission procedure tends to annoy us more -than amuse us. Spend your creative energy on content of your -submission rather than on the submission process itself.
We are often asked why the contest IOCCC rules and IOCCC -guidelines seem strange or contain mistakes, flaws or -grammatical errors. One reason is that we sometimes make genuine mistakes. But -in many cases such problems, flaws or areas of confusion are deliberate. -Changes to IOCCC rules and IOCCC guidelines in +guidelines seem strange or contain mistakes, flaws, or +grammatical errors. One reason is that we sometimes make genuine mistakes, but +in many cases such problems, flaws or areas of confusion are deliberate.
+Changes to IOCCC rules and IOCCC guidelines in response to rule abuses, are done in a minimal fashion. Often we will deliberately leave behind holes (or introduce new ones) so that future rule abuse can continue. A clever author should be able to read them and “drive a @@ -630,7 +602,7 @@ are only part of the overall contest. Even so, one might think the contest IOCCC rules and IOCCC guidelines process as a parody of the sometimes tragic mismatch between what a customer (or marketing) wants and what engineering delivers. Real programmers must face obfuscated and -sometimes conflicting specifications and requirements from marketing, sales, +sometimes conflicting, balloning specifications, and requirements from marketing, sales, product management and even from customers themselves on an all too regular basis. This is one of the reasons why the IOCCC rules and IOCCC guidelines are written in obfuscated form.
@@ -640,13 +612,13 @@ This is one of the reasons why the IOCCC rules andYou may use git, or services such as GitHub +
You may use git, or services such as GitHub
to develop and maintain your submission. However, we DISLIKE
submissions that require such services in order to build/compile your submission.
Submissions will be judged in an environment that has no IDE. Any submission that fails to compile/build because it requires an IDE will be rejected.
-We will use the make(1) tool, your Makefile, as well as tools found in the
+
We will use the GNU make(1) tool, your Makefile, as well as tools found in the
Single UNIX Specification
environments, and commonly found on systems that reasonably conform to the
Single UNIX Specification
@@ -664,7 +636,7 @@ course.
We STRONGLY recommend you do install the most recent release of mkiocccentry toolkit -as use of using older versions of the mkiocccentry toolkit to are HIGHLY LIKELY to be REJECTED!
+As use of using older versions of the mkiocccentry toolkit to are HIGHLY LIKELY to be REJECTED!If you submit your own JSON files (other than .auth.json and
.info.json) then they do NOT have to be valid JSON.
However, if you do provide invalid JSON files, PLEASE @@ -714,10 +686,12 @@ FAQ on “What are the detailed recommend FAQ on “What are the details behind Rule 17 - Use mkiocccentry?”.
Jump to: top
The IOCCC submit server, and related services use the most recent version of the mkiocccentry toolkit: @@ -725,10 +699,10 @@ submissions that package using older versions of the mkiocccentry toolkit are LIKELY to be REJECTED!
You REALLY SHOULD use the latest mkiocccentry toolkit +are LIKELY to be REJECTED! So you REALLY SHOULD use the latest mkiocccentry toolkit to package your own submission.
The mkiocccentry(1) tool runs a number of checks by way of these
-mkiocccentry toolkit
-tools:
Do NOT use txzchk(1) command line options that are labeled “for TESTING purposes”
-in the txzchk(1) man page.
Do NOT use txzchk(1) or fnamchk(1) command line options that are labeled
+“for TESTING purposes” in their respective man pages.
Do NOT use fnamchk(1) command line options that are labeled “for TESTING purposes”
in the fnamchk(1) man page.
Do NOT use chkentry(1) command line options that are labeled “for the use by the IOCCC judges only”
-in the chksubmit(1) (or chkentry(1)) man page(s).
chksubmit(1) (or chkentry(1)) man page(s).
+Similarly do NOT use chkentry(1) command line options marked “for the use
+by the IOCCC judges only” in the chkentry(1) man page.
To view mkiocccentry toolkit man pages, while your current directory is the top of the source tree:
- man soup/man/man1/mkiocccentry.1
- man soup/man/man1/iocccsize.1
- man soup/man/man1/txzchk.1
- man test_ioccc/man/man1/fnamchk.1
- man soup/man/man1/chksubmit.1
- man soup/man/man1/chkentry.1man soup/man/man1/mkiocccentry.1
+man soup/man/man1/iocccsize.1
+man soup/man/man1/txzchk.1
+man test_ioccc/man/man1/fnamchk.1
+man soup/man/man1/chksubmit.1
+man soup/man/man1/chkentry.1The above man(1) commands will show the toolkit man pages without having to install them first.
So that you do not have to repeatedly answer all the mkiocccentry(1) questions,
use mkiocccentry -a answers ... to create a file containing the answers you first give,
-that will allow you to later use mkiocccentry -i answers ... to reuse those same answers.
mkiocccentry -i answers ... to reuse those same answers.
The mkiocccentry -A answers ... does the same thing except that the answers file will be overwritten.
The mkiocccentry -i answers ... will still be required to confirm “Yes/No” questions.
Use mkiocccentry -Y -i answers .. to force a yes answers with great caution
because it might force a yes answer to something you do NOT want, such as a
-change in your code that violates a detected rule.
mkiocccentry -i answers .. will still be required to confirm “Yes/No” questions.
+While mkiocccentry -Y -i answers .. will force yes answers, use with great caution,
+because it might force a yes answer to something you do NOT want.
To help with not having to repeatedly enter a UUID, put your UUID into a file and use
mkiocccentry -u uuidfile ..., or use mkiocccentry -U UUID ... to give the UUID
on the command line.
If you wish to test that your submission passes the mkiocccentry(1) tests
-without having to type in in answers each time, you can use the -d or -s seed
+without having to type in answers each time, you can use the -d or -s seed
option to mkiocccentry for the tool to pseudo-randomly create answers for you.
For example:
mkiocccentry -d workdir topdirmkiocccentry -d workdir topdirDo NOT submit a tarball formed by mkiocccentry -d .. OR by
mkiocccentry -s seed .. OR by using the test UUID!
The mkiocccentry(1) tool creates an xz(1) compressed v7 format tarball using a tar(1)
command of the form:
cd workdir/UUID-slot_num && tar --format=v7 -cJf submit.UUID-slot_num.timestamp.txz UUID-slot_numcd workdir/UUID-slot_num && tar --format=v7 -cJf submit.UUID-slot_num.timestamp.txz UUID-slot_numIn many places the mkiocccentry(1) tool will prompt you to verify what you input, allowing you to
correct details as you go along.
Pressing the “enter key” at the mkiocccentry(1) tool prompts will allow you
@@ -785,7 +764,7 @@ run txzchk(1), which will also run fnamchk(1), as part
The use of mkiocccentry -W .... is highly discouraged as this may ignore
warnings about a problem that may cause your submission to be REJECTED!”
If mkiocccentry encounters an error, the program will exit and the xz
-compressed tarball will NOT be formed: this is a feature, not a bug!
If you encounter a bug with the
mkiocccentry toolkit
PLEASE run the bug_report.sh script to help us out here!
mkiocccentry(1) command line options to locate required tools
such as chkentry(1) (mkiocccentry -C chkentry ..), txzchk(1) (mkiocccentry -T txzchk ..),
and fnamchk(1) (mkiocccentry -F fnamchk ..).
-The mkiocccentry(1) tool will ignore any filename that begins with a “.” (dot).
The mkiocccentry(1) tool will ignore any directory tree with a directory name that begins with a “.” (dot).
The mkiocccentry(1) tool will all files that begin with COPYING, COPYRIGHT, and LICENSE, regardless
+
The mkiocccentry(1) tool will ignore any filename or directory that begins with a period (.).
The mkiocccentry(1) tool will ignore all files that begin with COPYING, COPYRIGHT, and LICENSE, regardless
of filename case.
The mkiocccentry(1) tool will reject any of the following files if they are found directly under
the top level directory (topdir):
See FAQ on “What is the mkiocccentry tool, how do I obtain it and how do I use it”.
Jump to: top
+ CSTD= -std=c99 OPT= -O0 -g3 # Common C compiler warning flags
+ #
+ CWARN= -Wall -Wextra ${CSILENCE} ${CUNKNOWN}-Weverything option CWARN= -Wall -Wextra -pedanticAll other things being equal, a program that must turn off fewer +warnings will be considered better, for certain values of better.
+ + CSILENCE= -Wno-some-thing -Wno-another-thing CSILENCE= -Wno-parentheses -Wno-binding-in-condition -Wno-misleading-indentation CUNKNOWN= CUNKNOWN= -Wno-unknown-warning-option CDEFINE= -Dfoo -Dbar=baz CINCLUDE= -include stdio.h COTHER= -fno-math-errnoThese guideline are hints and suggestions, NOT IOCCC rules.
While submissions that violate guideline are allowed, submissions that remain within the IOCCC guidelines are preferred.
@@ -922,10 +1166,12 @@ misleading comments and variable names might be a VERY GOOD STARTJump to: top
We VERY MUCH LIKE submissions that use an edited variant of the
example Makefile, as described and linked to in the Makefile section,
renamed as Makefile of course. This makes it easier for the IOCCC judges
@@ -1196,8 +1442,8 @@ MS Visual C and MS Visual C++ leave trailing control-M’s on lines.
Users of such tools should strip off such control-M’s before submitting
their submissions. In some cases tools have a “Save As” option that will
prevent such trailing control-M’s being added.
One should restrict libcurses to portable features found on BSD -or Linux curses.
+One should restrict libcurses to portable features found on both BSD +and Linux curses.
Try to be even more creative!
Jump to: top
The reason for the times of day are so that key IOCCC events are calculated to be a functional UTC time. :-)
At least 2 of several reasons for selecting the prime, 2503, for @@ -1412,10 +1659,12 @@ CPU, we might just try your submission on that emulator as well :-)
it? :-)Jump to: top
For questions or comments about the contest, see Contacting the IOCCC.
Be SURE to review the IOCCC Rules and Guidelines as they may (and often do) change from year to year.
diff --git a/next/guidelines.md b/next/guidelines.md index 6dc1dbb14..061ef30a8 100644 --- a/next/guidelines.md +++ b/next/guidelines.md @@ -1,31 +1,4 @@ - -# 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. - -These guidelines 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 guidelines. 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 -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. - - - # 29th International Obfuscated C Code Contest Official Guidelines All Rights Reserved. Permission for personal, education or non-profit use is -granted provided this this copyright and notice are included in its entirety +granted provided this copyright and notice are included in its entirety and remains unaltered. All other uses must receive prior permission in writing by [contacting the judges](../contact.html). -# IOCCC Guidelines version +# Guidelines VersionYou MUST register, using a valid email address, in order to submit @@ -553,7 +553,7 @@ to register! The judges are NOT responsible for delayed or lost email or for those who wait until the last minute to try to register!
See Entering the IOCCC: the bare minimum you need to know.
See Rule 8 - Submitting requirements.
-See Guidelines for Rule 3 - Registering for the IOCCC.
+See Guidelines for Rule 3 - Register for the IOCCC.
remarks.md file.
You are permitted to use tools to write your code.
-See Rule 16 - Anonymous Judging.
+See Rule 16 - Anonymous Judging.
See Guidelines for Rule 7 - Original Work.
See FAQ on “What are the detailed recommendations for a submission Makefile?”.
See Guidelines for Rule 15 - GNU Makefile compatibility.
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 diff --git a/next/rules.md b/next/rules.md index 0a3574ba5..68c519031 100644 --- a/next/rules.md +++ b/next/rules.md @@ -128,7 +128,7 @@ Use mkiocccentry](#rule17-mkiocccentry).