convert spoiler language and towards deobfuscation language

This commit is contained in:
Landon Curt Noll committed 2024-06-30 23:07:18 -07:00
1 parent 50a2a6293c
commit 4d6009b58f
98 files changed
+195 -358

No files matched your search

+1 -1
View File
@@ -259,7 +259,7 @@ a usage of `I` (complex's imaginary unit), but I bet this is cygwin's issue;
it is surely a C99 feature.
### Obfuscation w/ Spoiler
### Deobfuscation
First of all, the source code itself serves as an initial configuration.
Preprocessing directives (such as `#include`)'s `#` serve as walls.
+1 -1
View File
@@ -554,7 +554,7 @@ used to clear screen and move cursor to home.</p>
and gcc-4.5.3 and clang-3.1 on Cygwin. On Cygwin, gcc and clang complain about
a usage of <code>I</code> (complex’s imaginary unit), but I bet this is cygwin’s issue;
it is surely a C99 feature.</p>
<h3 id="obfuscation-w-spoiler">Obfuscation w/ Spoiler</h3>
<h3 id="deobfuscation">Deobfuscation</h3>
<p>First of all, the source code itself serves as an initial configuration.
Preprocessing directives (such as <code>#include</code>)’s <code>#</code> serve as walls.</p>
<p>This program uses <code>double complex</code> to represent any 2D vector. But, note that
+3 -2
View File
@@ -150,7 +150,7 @@ The design of the program explicitly allows for `EOF` even if it does not equal
endian-independent.
### Obfuscations (SPOILERS!)
### Debfuscation
Many obfuscations used are typical for standard IOCCC entries:
@@ -218,7 +218,8 @@ Having said this important trick, other details should be relatively easier to
follow. The order of lookup table, for example, is very important,
and the biggest constant 6177 is not arbitrarily chosen.
More spoilers can be found at <https://gist.github.com/lifthrasiir/3909337>
Even [more deobfuscation information](https://gist.github.com/lifthrasiir/3909337) is available.
### Acknowledgement
+2 -2
View File
@@ -493,7 +493,7 @@ character set and two’s complement representation.</li>
<code>-1</code> (it has to be negative per the standard but not necessarily <code>-1</code>) and both
<code>signed char</code> and <code>unsigned char</code>, for example. Furthermore it is
endian-independent.</p>
<h3 id="obfuscations-spoilers">Obfuscations (SPOILERS!)</h3>
<h3 id="debfuscation">Debfuscation</h3>
<p>Many obfuscations used are typical for standard IOCCC entries:</p>
<ul>
<li>Two arguments from <code>main()</code> function are reused as normal variables.</li>
@@ -547,7 +547,7 @@ one character.</li>
<p>Having said this important trick, other details should be relatively easier to
follow. The order of lookup table, for example, is very important,
and the biggest constant 6177 is not arbitrarily chosen.</p>
<p>More spoilers can be found at <a href="https://gist.github.com/lifthrasiir/3909337" class="uri">https://gist.github.com/lifthrasiir/3909337</a></p>
<p>Even <a href="https://gist.github.com/lifthrasiir/3909337">more deobfuscation information</a> is available.</p>
<h3 id="acknowledgement">Acknowledgement</h3>
<p>The cleaner (size-optimized) version of this program was originally published
in my website in July 2011. Sun Park and others have reviewed it and made me