cd 1991/dds and then do:
colordiff installed it’s a lot easier to see the differencesTo use these rules but provide a different diff, for instance colordiff,
just do:
make DIFF=colordiff diff_orig_prog # for orig to prog diff
- make DIFF=colordiff diff_alt_prog # for alt to prog diff make DIFF=colordiff diff_orig_prog # for orig to prog diff
+ make DIFF=colordiff diff_alt_prog # for alt to prog diffObviously if you want to view the alternate code or the orig code you can just open the files as described above.
These guidelines are a VERY TENTATIVE proposal for the next IOCCC and are VERY LIKELY to be updated before the next IOCCC. They are are provided as a VERY TENTATIVE hint at what -MIGHT be used in the next IOCCC.
-Please regard these guidelines as a historical archive.
+MIGHT be used in the next IOCCC. In some cases they might +even be a copy of the guidelines from the previous IOCCC.The IOCCC is NOT accepting new submissions at this time. See the IOCCC winning entries page for the entries that have won the @@ -404,7 +405,7 @@ granted provided this 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.
| These IOCCC guidelines are version 2024-06-25-v28.
| These IOCCC guidelines are version 28.1 2024-06-29.
IMPORTANT: Be SURE to read the IOCCC rules.
| ← Lines that start with this symbol indicate a change from the previous IOCCC
We do realize that there are holes in the rules, and invite entries to attempt to exploit them. We will award ‘Worst abuse of the rules’ or ‘Best abuse of the rules’ and then plug the hole next year.
-| Even so, we will attempt to use the smallest plug needed, if not smaller. Or, maybe not. :-)
| 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. :-)
| There may be less than 2^7+1 reasons why these IOCCC guidelines seem obfuscated.
Check out your program and be sure that it works. We sometimes make the effort to debug an submission that has a slight problem, particularly @@ -656,7 +659,8 @@ not portable and must not be used:
va_list as a structure or unionIn particular, do not treat va_list variables as if they were a char **s.
Avoid using varargs.h. Use stdarg.h instead.
| We DISLIKE the use of varargs.h. Use stdarg.h instead.
| We DISLIKE the use of gets(3). Use fgets(3) instead.
On 28 January 2007, the Judges rescinded the requirement that the
# in a C preprocessor directive must be the 1st non-whitespace octet.
The exit(3) function returns void. Some broken systems have exit(3)
@@ -816,7 +820,7 @@ partly misunderstand this particular guideline, but of course, we could
not possibly comment! :-) Nevertheless, you are neither prohibited, nor are
you fully required to determine that this or the previous sentence is either false
and/or perhaps misleading. Therefore, it might be wise for you to not fail to
-consider to do so, accordingly. Thank you very much.
Any complaints about the above guideline could be addressed to the Speaker of the House of Commons, or to the speaker of your national @@ -899,8 +903,8 @@ a PDP-11. Heck, should we ever find an emulator of 60-bit CDC Cyber CPU, we might just try your submission on that emulator as well :-)
| If your submission MUST run only on a 64-bit or 32-bit architecture,
then you MUST specify the -arch on your command line
-(see CARCH in the example Makefile. Do not assume a processor word size without specifying -arch. For example:
CARCH= -m64ARCH in the example Makefile. Do not assume a processor word size without specifying -arch. For example:
+ ARCH= -m64| Try to be even more creative!
| If there are limitations in your submission, you are highly encouraged
to note such limitations in your remarks.md file. For example if your
diff --git a/next/guidelines.md b/next/guidelines.md
index 7e8c6eae6..f143da669 100644
--- a/next/guidelines.md
+++ b/next/guidelines.md
@@ -1,11 +1,12 @@
+
+
# WARNING: These guidelines are OUT OF DATE
These guidelines are a **VERY TENTATIVE proposal** for the next IOCCC
and are **VERY LIKELY** to be updated before the next IOCCC.
They are are provided as a **VERY TENTATIVE** hint at **what
-MIGHT** be used in the next IOCCC.
-
-Please regard these guidelines as a historical archive.
+MIGHT** be used in the next IOCCC. In some cases they might
+even be a copy of the guidelines from the previous IOCCC.
# The IOCCC is closed
@@ -32,7 +33,7 @@ writing by [contacting the judges](../contact.html).
## IOCCC Guidelines version
-**`|`** These [IOCCC guidelines](guidelines.html) are version **2024-06-25-v28**.
+**`|`** These [IOCCC guidelines](guidelines.html) are version **28.1 2024-06-29**.
**IMPORTANT**: Be **SURE** to read the [IOCCC rules](rules.html).
@@ -149,7 +150,9 @@ We do realize that there are holes in the rules, and invite entries
to attempt to exploit them. We will award '_Worst abuse of the rules_' or
'_Best abuse of the rules_' and then plug the hole next year.
-**`|`** Even so, we will attempt to use the smallest plug needed, if not smaller. Or, maybe not. :-)
+**`|`** When we do need to plug a hole in the [IOCCC rules](rules.html)
+or [IOCCC guidelines](guidelines.html), we will attempt to use a very
+small plug, if not smaller. Or, maybe not. :-)
**`|`** There may be less than 2^7+1 reasons why these [IOCCC guidelines](guidelines.html) seem obfuscated.
@@ -264,7 +267,7 @@ compiler! We often start by compiling using the **clang** C compiler instead.
**`|`** You may change the standard under which your submission is compiled
by modifying the `CSTD` Makefile variable. For example, to use `c17` instead:
-```
+```
CSTD= -std=c17
```
@@ -277,7 +280,7 @@ your submission's `Makefile`.
which your submission is compiled by modifying the `COPT` Makefile variable.
For example, to compile without optimization:
-```
+```
COPT= -O0 -g3
```
@@ -289,7 +292,7 @@ warning, try not fret too much.
**`|`** To turn off a compiler warning, to your submission's `Makefile`,
try something such as:
-```
+```
CSILENCE= -Wno-some-thing -Wno-another-thing -Wno-unknown-warning-option
```
@@ -301,14 +304,14 @@ submission.
**`|`** If you need to define something on the compile line, use
the `CDEFINE` Makefile variable. For example:
-```
+```
CDEFINE= -Dfoo -Dbar=baz
```
**`|`** If you need to include a file on the command line, use
the `CINCLUDE` Makefile variable. For example:
-```
+```
CINCLUDE= -include stdio.h
```
@@ -316,7 +319,7 @@ the `CINCLUDE` Makefile variable. For example:
**`|`** If need add other "_magic_" flags to your compile line,
use the `COTHER` Makefile variable. For example:
-```
+```
COTHER= -fno-math-errno
```
@@ -354,7 +357,7 @@ When declaring local or global variables, you should declare the type:
**`|`** We **LIKE** code that has a minimum of warnings, especially under the
more strict ` -Wall -Wextra -pedantic` mode:
-```
+```
CWARN= -Wall -Wextra -pedantic
```
@@ -408,7 +411,9 @@ not portable and must not be used:
In particular, do not treat `va_list` variables as if they were a `char **`s.
-Avoid using `varargs.h`. Use `stdarg.h` instead.
+**`|`** We **DISLIKE** the use of `varargs.h`. Use `stdarg.h` instead.
+
+**`|`** We **DISLIKE** the use of `gets(3)`. Use `fgets(3)` instead.
On 28 January 2007, the Judges rescinded the requirement that the
`#` in a C preprocessor directive must be the 1st non-whitespace octet.
@@ -630,7 +635,7 @@ particular window manager.
> not possibly comment! :-) Nevertheless, you are neither prohibited, nor are
> you fully required to determine that this or the previous sentence is either false
> and/or perhaps misleading. Therefore, it might be wise for you to not fail to
-> consider to do so, accordingly. Thank you very much.
+> consider to not do so, accordingly. Thank you very much.
Any complaints about the above _guideline_ could be addressed to the
Speaker of the House of Commons, or to the speaker of your national
@@ -733,10 +738,10 @@ CPU, we might just try your submission on that emulator as well :-)
**`|`** If your submission **MUST** run only on a 64-bit or 32-bit architecture,
then you **MUST** specify the `-arch` on your command line
-(see `CARCH` in the [example Makefile](https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example). Do not assume a processor word size without specifying `-arch`. For example:
+(see `ARCH` in the [example Makefile](https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example). Do not assume a processor word size without specifying `-arch`. For example:
-```
- CARCH= -m64
+```
+ ARCH= -m64
```
**`|`** Try to be even more creative!
diff --git a/next/rules.html b/next/rules.html
index ddce63146..a650d81f0 100644
--- a/next/rules.html
+++ b/next/rules.html
@@ -387,7 +387,8 @@
These rules are a VERY TENTATIVE proposal for the next IOCCC and are VERY LIKELY to be updated before the next IOCCC. They are are provided as a very tentative hint at what -MIGHT be used in the next IOCCC.
+MIGHT be used in the next IOCCC. In some cases they might +even be a copy of the rules from the previous IOCCC.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 @@ -406,7 +407,7 @@ writing by contacting the judges.
| These IOCCC rules are version 2024-06-25-v28.
| These IOCCC rules are version 28.1 2024-06-29.
IMPORTANT: Be sure to read the IOCCC guidelines.
| ← Lines that start with this symbol indicate a change from the previous IOCCC
Programs that require special privileges (setuid(2), setgid(2), super-user,
-special owner, special group, etc.) are still highly discouraged. We
-do not guarantee these functions will behave as you expect on our test
-platforms. If your program needs special permissions please document
-them in the remarks file.
Programs that require special privileges (setuid(2), setgid(2),
+super-user, special owner, special group, etc.) are still 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 submissions remarks.md file.
remarks.md file.Rule 13
| Any C source that fails to compile because of unescaped octets with
-the high bit set (octet value >= 128) might be rejected.
| Any C source that fails to compile because of lines with trailing
-control-M’s (i.e., lines with a tailing octet 015) might be rejected.
015) might be rejected.
Please do NOT put trailing control-M’s on remarks file lines. Please check to be sure, before submitting, that you have removed any control-M at the end of remark file lines.
diff --git a/next/rules.md b/next/rules.md index 547cb4625..06160303b 100644 --- a/next/rules.md +++ b/next/rules.md @@ -5,7 +5,8 @@ These rules are a **VERY TENTATIVE proposal** for the next IOCCC and are **VERY LIKELY** to be updated before the next IOCCC. They are are provided as a **very tentative** hint at **what -MIGHT** be used in the next IOCCC. +MIGHT** be used in the next IOCCC. In some cases they might +even be a copy of the rules from the previous IOCCC. # The IOCCC is closed @@ -34,7 +35,7 @@ writing by [contacting the judges](../contact.html). ## IOCCC Rules version -**`|`** These [IOCCC rules](rules.html) are version **2024-06-25-v28**. +**`|`** These [IOCCC rules](rules.html) are version **28.1 2024-06-29**. **IMPORTANT**: Be sure to read the [IOCCC guidelines](guidelines.html). @@ -294,11 +295,12 @@ Entries requiring human interaction to be initially compiled are not permitted. ## Rule 11 -Programs that require special privileges (`setuid(2)`, `setgid(2)`, super-user, -special owner, special group, etc.) are still highly discouraged. We -do not guarantee these functions will behave as you expect on our test -platforms. If your program needs special permissions **please document -them** in the remarks file. +Programs that require special privileges (`setuid(2)`, `setgid(2)`, +super-user, special owner, special group, etc.) are still **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 submissions `remarks.md` file.