convert spoiler language and towards deobfuscation language
This commit is contained in:
1 parent
50a2a6293c
commit
4d6009b58f
98 files changed
+195
-358
No files matched your search
@@ -198,7 +198,8 @@ Just say
|
||||
|
||||
(Btw, tcc has its roots in IOCCC...)
|
||||
|
||||
### Obfuscations (a.k.a. spoilers...)
|
||||
|
||||
### Deobfuscation
|
||||
|
||||
* The initialized char array includes the source code of the real program,
|
||||
as well as its name and commands to build and run it, all
|
||||
|
||||
@@ -536,7 +536,7 @@ C99, or long lines as an extension. This code has been tested on:</p></li>
|
||||
<li><p>AIX 5.3, IBM eServer p5-550, gcc 3.3.3 and AIX CC Version 6</p>
|
||||
<p>(Btw, tcc has its roots in IOCCC…)</p></li>
|
||||
</ul>
|
||||
<h3 id="obfuscations-a.k.a.-spoilers">Obfuscations (a.k.a. spoilers…)</h3>
|
||||
<h3 id="deobfuscation">Deobfuscation</h3>
|
||||
<ul>
|
||||
<li>The initialized char array includes the source code of the real program,
|
||||
as well as its name and commands to build and run it, all
|
||||
|
||||
+1
-1
@@ -110,7 +110,7 @@ the actual `argv` strings to be writable, though.
|
||||
- Some seemingly redundant code works to eliminate warnings and evade a gcc bug.
|
||||
|
||||
|
||||
### Spoilers
|
||||
### Deobfuscation
|
||||
|
||||
The parser parses function names, subtraction, and division as single-letter
|
||||
unary operators. A bitmask encoded hash table is used to check no-ops/digits
|
||||
|
||||
+1
-1
@@ -462,7 +462,7 @@ the actual <code>argv</code> strings to be writable, though.</li>
|
||||
<li>This program doesn’t work with <code>%e</code> style numbers like <code>1e-4</code>.</li>
|
||||
<li>Some seemingly redundant code works to eliminate warnings and evade a gcc bug.</li>
|
||||
</ul>
|
||||
<h3 id="spoilers">Spoilers</h3>
|
||||
<h3 id="deobfuscation">Deobfuscation</h3>
|
||||
<p>The parser parses function names, subtraction, and division as single-letter
|
||||
unary operators. A bitmask encoded hash table is used to check no-ops/digits
|
||||
and another hash function maps the ASCII to a function ordinal, which is then
|
||||
|
||||
@@ -153,7 +153,7 @@ reflection ray at an object's surface, given the incoming
|
||||
direction and surface normal.
|
||||
|
||||
|
||||
#### Further details (contains spoilers):
|
||||
#### Further deobfuscation:
|
||||
|
||||
The program is not quite a traditional [ray
|
||||
tracer](https://en.wikipedia.org/wiki/Ray_tracing_(graphics)), but a "[sphere
|
||||
|
||||
@@ -480,7 +480,7 @@ by the source code itself: the geometric construction of a
|
||||
reflection ray at an object’s surface, given the incoming
|
||||
direction and surface normal.</p></li>
|
||||
</ul>
|
||||
<h4 id="further-details-contains-spoilers">Further details (contains spoilers):</h4>
|
||||
<h4 id="further-deobfuscation">Further deobfuscation:</h4>
|
||||
<p>The program is not quite a traditional <a href="https://en.wikipedia.org/wiki/Ray_tracing_(graphics)">ray
|
||||
tracer</a>, but a “<a href="sphere-tracing.pdf">sphere
|
||||
tracer</a>” which uses distance fields to encode proximity to
|
||||
|
||||
Reference in new issue
Block a user