IMPORTANT: Be SURE to read the IOCCC rules.
In cases where the above summary and the algorithm implemented by the IOCCC size tool source code conflict, the algorithm implemented -by the IOCCC size tool source code is preferred by the judges.
+by the IOCCC size tool source code is preferred by the judges. } | please_dont_submit_this(); } -On 2012 July 20, the judges rescinded the encouragement of +
On 2012 July 20, the judges rescinded the encouragement of
nested functions. Such constructions, while interesting and sometimes
amusing, will have to wait until they required by a C standard that are
actually implemented in BOTH gcc AND clang.
The judges, as a group, have a history giving wide degree of latitude +
The judges, as a group, have a history giving wide degree of latitude to reasonable entries. And recently they have had as much longitudinal variation as it is possible to have on Earth. :-)
-You are in a maze of twisty guidelines, all different.
There are at least zero judges who think that +
There are at least zero judges who think that Fideism has little or nothing to do with the IOCCC judging process.
Don’t forget that the building of your program should be done @@ -1366,7 +1366,7 @@ Noll, might run the risk of violating Rule 7 does not prohibit you from writing your own obfuscated versions of these tools, unless of course you are Landon Curt Noll, in which case you probably won’t -win since judges are disqualified! :-) +win since judges are disqualified! :-) However, if you do write your own version, you might wish to make it do something more interesting than simply implementing the IOCCC tools’ algorithms. On the other hand, writing an obfuscated version of a library runs the risk of violating @@ -1414,7 +1414,7 @@ produce unpredictable results.
2305567963945518424753102147331756070. Attempting to factor values outside
that range will produce unpredictable results.
-Moreover the try to also factor 3.5 or 0x7, or Fred, so you want to might state:
+Moreover the might try to also factor 3.5 or 0x7, or Fred, so you want to might state:
This submission factors integers between 1 and
2305567963945518424753102147331756070. Attempting to factor anything else @@ -1490,7 +1490,7 @@ entries, 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 judges, WILL be +opinion of the 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 @@ -1509,7 +1509,7 @@ submitting an alternate version that conforms to the If you do bypass the
mkiocccentry(1)warnings about Rule 2a and/or about Rule 2b and submit a submission anyway, you MUST try to justify why the IOCCC -judges should not reject your submission due to a rule violation. +judges should not reject your submission due to a rule violation.Abusing the web submission procedure tends to annoy us more than amuse us. Spend your creative energy on content of your @@ -1542,7 +1542,7 @@ This is one of the reasons why the IOCCC rules and submission files including, but not limited to
-prog.c,Makefile,remarks.mdas well as any data files that you submit, are all placed under their own directory and stored and judged from this directory.Any information about the authors is not read by the judges until +
Any information about the authors is not read by the judges until the judging process is complete, and then only from entries that have won an award. Because we do not read this information for entries that do not win, we do not know who did not win.
@@ -1554,7 +1554,7 @@ about the others. However we consider this to be simply circumstantial and outside the scope of the above paragraph.Some people, in the past, have attempted to obfuscate their identity by including comments of famous Internet personalities such as Peter -Honeyman. The judges are on to this trick +Honeyman. The judges are on to this trick and therefore consider any obfuscated source or data file claiming to be from Honeyman to not be from Honeyman. This of course creates an interesting paradox known as the “obfuscated Peter Honeyman paradox”. Should Peter Honeyman diff --git a/next/guidelines.md b/next/guidelines.md index b869ac8b8..a68ef830b 100644 --- a/next/guidelines.md +++ b/next/guidelines.md @@ -46,7 +46,7 @@ writing by [contacting the judges](../contact.html).
IMPORTANT: Be sure to read the IOCCC guidelines.
remarks.md file.
Legal abuse of the rules is somewhat encouraged. A submission that, in
-the opinion of the judges, violates the rules will be disqualified.
+the opinion of the judges, violates the rules will be disqualified.
Submissions that attempt to abuse the rules MUST** try to justify why
their rule abuse is legal, in the remarks.md file.
The judges are not responsible for delays in email, please plan +
The judges are not responsible for delays in email, please plan enough time for one automated exchange of email as part of your submission.
Catch 22:
Your source code, data files, remarks and program output MUST NOT -identify the authors of your code. The judges STRONGLY PREFER to +identify the authors of your code. The judges STRONGLY PREFER to NOT know who is submitting entries to the IOCCC.
Even if you are a previous IOCCC winner, catch 22 still applies.
Identifying the author(s) of your submission in an obvious way anywhere diff --git a/next/rules.md b/next/rules.md index b08525094..b7ec5ff79 100644 --- a/next/rules.md +++ b/next/rules.md @@ -46,7 +46,7 @@ writing by [contacting the judges](../contact.html).
**IMPORTANT**: Be sure to read the [IOCCC guidelines](guidelines.html). @@ -387,7 +387,7 @@ it is needed in your submissions `remarks.md` file. **Legal** abuse of the rules is somewhat encouraged. **A submission that, in -the opinion of the judges, **violates the rules will be disqualified**. +the opinion of the [judges](../judges.html), **violates the rules will be disqualified**. Submissions that attempt to abuse the rules **MUST** try to justify why their rule abuse is legal, in the `remarks.md` file. @@ -424,7 +424,7 @@ any control-M at the end of remark file lines. In order to register for the IOCCC, you **MUST** have a valid email address. -The judges **are not responsible for delays in email**, please plan +The [judges](../judges.html) **are not responsible for delays in email**, please plan enough time for one automated exchange of email as part of your submission. @@ -794,7 +794,7 @@ directory name or filename you create. Catch 22: Your source code, data files, remarks and program output **MUST NOT** -identify the authors of your code. The judges **STRONGLY PREFER** to +identify the authors of your code. The [judges](../judges.html) **STRONGLY PREFER** to **NOT** know who is submitting entries to the IOCCC. Even if you are a previous IOCCC winner, catch 22 still applies.