We also suggest that you take a very good look at how the muth code makes full use of the C Pre-Processor.
-…We’ll stop spouting spoilers now. Have fun exploring all the entries!
+…We’ll stop spouting deobfuscation information now. Have fun exploring all the entries!
The number of entries that would have made it into the final rounds would have been much higher had some people paid attention to rules 2 diff --git a/2018/README.md b/2018/README.md index 2cba6c9ae..f87192dc9 100644 --- a/2018/README.md +++ b/2018/README.md @@ -42,7 +42,7 @@ The [Most likely to be awarded - 2018/ciura](ciura/index.html) has an amazing vo There are also nods to entries of the years [2000/bellard](../2000/bellard/index.html), [2015/yang](../2015/yang/index.html), ... -...We'll stop spouting spoilers now. Have fun exploring all the entries! +...We'll stop spouting deobfuscation information now. Have fun exploring all the entries! ## Remarks on some of submissions that did not win diff --git a/2018/index.html b/2018/index.html index 3cc051333..a39b8d6f1 100644 --- a/2018/index.html +++ b/2018/index.html @@ -414,7 +414,7 @@ It is something completely different.
The Most likely to be awarded - 2018/ciura has an amazing vocabulary!
There are also nods to entries of the years 2000/bellard, 2015/yang, …
-…We’ll stop spouting spoilers now. Have fun exploring all the entries!
+…We’ll stop spouting deobfuscation information now. Have fun exploring all the entries!
The number of entries that would have made it into the final rounds would have been much higher had some people paid attention to rules 2 diff --git a/2019/README.md b/2019/README.md index e9ad4f2f7..b3f961357 100644 --- a/2019/README.md +++ b/2019/README.md @@ -38,7 +38,7 @@ These nods to not run afoul of the guideline: because the entry [2019/dogon](dogon/index.html) appropriately pays homage to past entries without blatantly reusing their code. -...We'll stop spouting spoilers now. Have fun exploring all the entries! +...We'll stop spouting deobfuscation information now. Have fun exploring all the entries! ## Remarks on some of submissions that did not win diff --git a/2019/index.html b/2019/index.html index 2f1bdaf49..0124d9510 100644 --- a/2019/index.html +++ b/2019/index.html @@ -415,7 +415,7 @@ are rather similar to previous entries
because the entry 2019/dogon appropriately pays homage to past entries without blatantly reusing their code.
-…We’ll stop spouting spoilers now. Have fun exploring all the entries!
+…We’ll stop spouting deobfuscation information now. Have fun exploring all the entries!
Some entries tried to get around the size limit by submitting a data file that was really C code and then blindly including code in prog.c.
diff --git a/2020/README.md b/2020/README.md index 41b12342d..db3a30775 100644 --- a/2020/README.md +++ b/2020/README.md @@ -27,7 +27,7 @@ and [Snake - 2020/ferguson1](ferguson1/index.html). An entry, [kurdyukov1](kurdyukov1/index.html), pays homage to the previous entry [2015/hou](../2015/hou/index.html). -...We'll stop spouting spoilers now. Have fun exploring all the entries! +...We'll stop spouting deobfuscation information now. Have fun exploring all the entries! ## Remarks on some of submissions that did not win diff --git a/2020/ferguson1/HACKING.html b/2020/ferguson1/HACKING.html index 642636eac..4cd1dd451 100644 --- a/2020/ferguson1/HACKING.html +++ b/2020/ferguson1/HACKING.html @@ -495,7 +495,7 @@ left it might be: Please note that modifier keys like ctrl aren’t detectable or at least I’m unaware of how to do so.Below I give a table of some variables/expressions along with the data types and their respective format specifiers of the data. Originally it was a lot more detailed but as I started obfuscating things variables started to disappear and diff --git a/2020/ferguson1/HACKING.md b/2020/ferguson1/HACKING.md index cc67b45e3..76848223c 100644 --- a/2020/ferguson1/HACKING.md +++ b/2020/ferguson1/HACKING.md @@ -152,7 +152,7 @@ unaware of how to do so. ## Modifying the status/score line (table of variables/stats below) -### SPOILER WARNING +### DEOBFUSCATION NOTICE Below I give a table of some variables/expressions along with the data types and their respective format specifiers of the data. Originally it was a lot more diff --git a/2020/ferguson1/gameplay.html b/2020/ferguson1/gameplay.html index ae8128c40..6301d2d74 100644 --- a/2020/ferguson1/gameplay.html +++ b/2020/ferguson1/gameplay.html @@ -802,7 +802,7 @@ to be a problem simply do:
could also set the max size to be the highest possible by saying MAXSIZE=-1Which I’ve done in the play.sh script.
-I discuss how this mode works in [spoilers.markdown][].
+I discuss how this mode works in spoilers.html.
Here’s an example run where I spelt ‘SNAKE’. As you can see it’s far from perfect: the snake after all does not leave gaps and the game does not support diagonal movement and I also made a mistake and had to modify what I was aiming diff --git a/2020/ferguson1/gameplay.md b/2020/ferguson1/gameplay.md index 3a1234e48..18e955ad8 100644 --- a/2020/ferguson1/gameplay.md +++ b/2020/ferguson1/gameplay.md @@ -554,7 +554,7 @@ could also set the max size to be the highest possible by saying Which I've done in the [play.sh][] script. -I discuss how this mode works in [spoilers.markdown][]. +I discuss how this mode works in [spoilers.html][]. Here's an example run where I spelt 'SNAKE'. As you can see it's far from perfect: the snake after all does not leave gaps and the game does not support diff --git a/2020/index.html b/2020/index.html index 1cb6b00fe..7746ce891 100644 --- a/2020/index.html +++ b/2020/index.html @@ -405,7 +405,7 @@ IOCCC list!
and Snake - 2020/ferguson1.An entry, kurdyukov1, pays homage to the previous entry 2015/hou.
-…We’ll stop spouting spoilers now. Have fun exploring all the entries!
+…We’ll stop spouting deobfuscation information now. Have fun exploring all the entries!
As a rule, we try to compile the entries on a variety of platforms. Quite a few entries this year could not be built or executed on some of them due to reliance diff --git a/README.html b/README.html index 481405f87..749afc324 100644 --- a/README.html +++ b/README.html @@ -484,9 +484,10 @@ the top of the index.html for each entry as well. Keep in mind that C compilers often have bugs, or features which result the program failing to compile. You may have to do some syntax changing as we did to get old programs to compile on strict ANSI C compilers.
-Last, read the judges’ remarks/spoilers on the program. Hints for foo.c are
+
Last, read the judges’ remarks and deobfuscation information on the program. Hints for foo.c are
given in index.html. Often they will contain suggested arguments or
-recommended data to use. Authors also sometimes give spoilers.
If you do gain some understanding of how a program works, go back to the source and reexamine it using some of the techniques outlined above. See if you can convince yourself of why the program does what it does.
diff --git a/README.md b/README.md index 58f69bc30..2d01c365a 100644 --- a/README.md +++ b/README.md @@ -128,9 +128,10 @@ often have bugs, or features which result the program failing to compile. You may have to do some syntax changing as we did to get old programs to compile on strict ANSI C compilers. -Last, read the judges' remarks/spoilers on the program. Hints for `foo.c` are +Last, read the judges' remarks and deobfuscation information on the program. Hints for `foo.c` are given in `index.html`. Often they will contain suggested arguments or -recommended data to use. Authors also sometimes give spoilers. +recommended data to use. Authors also sometimes provide deobfuscation information +about their entries. If you do gain some understanding of how a program works, go back to the source and reexamine it using some of the techniques outlined above. See if you can diff --git a/bugs.html b/bugs.html index be12cac89..e7d43a340 100644 --- a/bugs.html +++ b/bugs.html @@ -2811,8 +2811,8 @@ used.Also, it requires a space between identifiers. In short, use (S K) instead of
(SK), “`sk”, **iiiiiiiii, or11111100011100`.
Huge memory may be required to compile the program (about 300 MB on my machine).
-In addition, there are some limitations (and workarounds) mentioned in Spoiler -section.
+In addition, there are some limitations (and workarounds) mentioned in the +Deobfuscation section.
–
IMPORTANT: When you ask your question (in public or as a private question) -PLEASE try to NOT spoil the surprise of your pending submission. +PLEASE try to NOT discuss detailed about your pending submission. Try to ask for question in a more generic way as this will help others with a similar question and this will not give away what you might be doing with your submission. If the IOCCC judges truly need more diff --git a/faq.md b/faq.md index 42bf71427..4a07311d8 100644 --- a/faq.md +++ b/faq.md @@ -504,7 +504,7 @@ then use the [How to contact the IOCCC](contact.html) information to ask a private question. **IMPORTANT**: When you ask your question (in public or as a private question) -**PLEASE** try to **NOT** spoil the surprise of your pending submission. +**PLEASE** try to **NOT** discuss detailed about your pending submission. Try to ask for question in a more generic way as this will help others with a similar question and this will not **give away** what you might be doing with your submission. If the [IOCCC judges](judges.html) truly need more diff --git a/thanks-for-help.html b/thanks-for-help.html index a4ddf0d81..e475580a5 100644 --- a/thanks-for-help.html +++ b/thanks-for-help.html @@ -2118,9 +2118,9 @@ primes.
Cody converted the spoiler compiler options (provided by the author) to be +
Cody converted the deobfuscation compiler options (provided by the author) to be compiler commands and added a script try.sh to -automate the spoiler commands to make it easier to see the game in action from +automate the deobfuscation commands to make it easier to see the game in action from start to finish.
Cody also added the alternate version that will look fine on terminals not set to 80 columns and the @@ -2183,7 +2183,7 @@ added.
At our change in how to deal with spoilers, Cody also uudecoded the spoiler provided +
At our change in how to deal with deobfuscation, Cody also uudecoded the deobfuscation inforation provided by the author, putting it in spoiler.html.
Cody added the authors’ spoiler as a C -file as in 2023 we have decided that in most +
Cody added the authors’ deobfuscation source code +as in 2023 we have decided that in most cases all the code should be available for the wider audience, without having to extract it. The exception is when the files are created by the entry or the entry decrypts the text or something like that.
@@ -2466,7 +2466,7 @@ this not only lets it work with systems withoutgcc (though in macO
exist but is actually clang) as cc always should.
Getting this entry to work was quite complicated but is also very interesting.
To see how the macOS fixes works, see the macos.html -file but do note that this includes spoilers for both versions! The fixes to get +file but do note that this includes deobfuscation information for both versions! The fixes to get it to work at all are described next.
So what was wrong with the original?
The call to freopen(3) was incorrect with the second arg (the mode) being
@@ -4012,7 +4012,7 @@ symbols from being built with rake Cody also updated the
Rakefile slightly.
Barely worth noting but done nonetheless, Cody renamed the read_me.html
file to spoilers.html to be clearer in its purpose as
-it is a file with spoilers (and too close to index.html?).
Cody added the try.sh script. This script will ask
-if the user wants to see some of the spoilers and only show them if they type
+if the user wants to see some of the deobfuscation information and only show them if they type
y or Y.
He also added the try.sh script.
He also made it possible to easily redefine the memory macro Z at compilation
time by improving the Makefile.
He fixed a link in the spoiler source code. As a spoiler it felt more important +
He fixed a link in the deobfuscation source code. It felt more important that this was done (some typos were fixed as well but only some - the purpose was to only correct spelling and only some, not to change wording or anything else).
diff --git a/thanks-for-help.md b/thanks-for-help.md index 6ce544d42..e564d6862 100644 --- a/thanks-for-help.md +++ b/thanks-for-help.md @@ -2455,9 +2455,9 @@ primes. ### Winning entry source code: [westley.c](%%REPO_URL%%/1994/westley/westley.c)