Reword the recent deobfuscation changes
In most cases the word was changed to 'obfuscation' as it was about
obfuscation, not deobfuscation. In some cases like 1995/leo since the
file was (in 1995/leo) about a secret switch it was changed to
'secret.md' (and 'secret.html') but there were others like that as well.
One entry had the words 'spoiling the size rule' but this had been
changed to 'deobfuscating the size rule' which was obviously wrong.
In the latter YYYY/README.md files the judges had written after some
entries (brief summaries) '...
...We'll stop spouting spoilers now. Have fun exploring all the
entries!
but that was changed to:
...We'll stop spouting deobfuscation information now. Have fun
exploring all the entries!
which wasn't really about deobfuscation but just a brief summary of what
the entries did.
And in the most problematic case (at least for me :-), 2018/ferguson) I
had put a joke in:
... but it's the only Easter egg I won't spoil
but it was changed to 'won't deobfuscate' which not only is not what it
is but it spoilt the joke.
In some cases the word was changed back to 'SPOILER' (or similar) but in
most cases not. I believe it should be better now. There are some
caveats, however, as below.
Although make find_missing_links is okay I do not remember if this will
catch links that refer to '%%REPO_URL%%' or other pandoc tokens. This
means I might have to go back to some earlier years to verify links are
okay. That should not take that much time I hope.
It might also be that some wording can still be improved some but it is
hoped this will be discovered when checking links and looking over the
manifest (which obviously changed).
This commit is contained in:
1 parent
a379c6296a
commit
1ac055fa85
193 files changed
+531
-524
No files matched your search
+1
-1
@@ -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 deobfuscation information now. Have fun exploring all the entries!
|
||||
...We'll stop spouting spoilers now. Have fun exploring all the entries!
|
||||
|
||||
|
||||
## Remarks on some of submissions that did not win
|
||||
|
||||
@@ -66,7 +66,7 @@
|
||||
"entry_text" : "sample input"
|
||||
},
|
||||
{
|
||||
"file_path" : "deobfuscation/code.c",
|
||||
"file_path" : "obfuscation/code.c",
|
||||
"inventory_order" : 200,
|
||||
"OK_to_edit" : true,
|
||||
"display_as" : "c",
|
||||
@@ -74,7 +74,7 @@
|
||||
"entry_text" : "debofuscated code main logic"
|
||||
},
|
||||
{
|
||||
"file_path" : "deobfuscation/gen.rb",
|
||||
"file_path" : "obfuscation/gen.rb",
|
||||
"inventory_order" : 200,
|
||||
"OK_to_edit" : true,
|
||||
"display_as" : "ruby",
|
||||
@@ -82,7 +82,7 @@
|
||||
"entry_text" : "ruby code to compose items and prog.c in artistic way"
|
||||
},
|
||||
{
|
||||
"file_path" : "deobfuscation/glyphs.txt",
|
||||
"file_path" : "obfuscation/glyphs.txt",
|
||||
"inventory_order" : 200,
|
||||
"OK_to_edit" : true,
|
||||
"display_as" : "text",
|
||||
@@ -90,7 +90,7 @@
|
||||
"entry_text" : "glyphs data for deobfuscation/gen.rb"
|
||||
},
|
||||
{
|
||||
"file_path" : "deobfuscation/index.html",
|
||||
"file_path" : "obfuscation/index.html",
|
||||
"inventory_order" : 200,
|
||||
"OK_to_edit" : true,
|
||||
"display_as" : "html",
|
||||
@@ -98,7 +98,7 @@
|
||||
"entry_text" : "deobfuscation information web page"
|
||||
},
|
||||
{
|
||||
"file_path" : "deobfuscation/prog.c",
|
||||
"file_path" : "obfuscation/prog.c",
|
||||
"inventory_order" : 200,
|
||||
"OK_to_edit" : true,
|
||||
"display_as" : "c",
|
||||
@@ -106,7 +106,7 @@
|
||||
"entry_text" : "deobfuscated source code"
|
||||
},
|
||||
{
|
||||
"file_path" : "deobfuscation/tmpl.txt",
|
||||
"file_path" : "obfuscation/tmpl.txt",
|
||||
"inventory_order" : 200,
|
||||
"OK_to_edit" : true,
|
||||
"display_as" : "text",
|
||||
@@ -154,7 +154,7 @@
|
||||
"entry_text" : "markdown source for this web page"
|
||||
},
|
||||
{
|
||||
"file_path" : "deobfuscation/index.md",
|
||||
"file_path" : "obfuscation/index.md",
|
||||
"inventory_order" : 4000000000,
|
||||
"OK_to_edit" : true,
|
||||
"display_as" : "markdown",
|
||||
|
||||
@@ -115,7 +115,8 @@ ENTRY= endoh2
|
||||
PROG= prog
|
||||
#
|
||||
OBJ= ${PROG}.o
|
||||
DATA= bear.txt hello.txt yoda.txt
|
||||
DATA= bear.txt hello.txt yoda.txt obfuscation/code.c obfuscation/gen.rb obfuscation/glyphs.txt \
|
||||
obfuscation/index.md obfuscation/prog.c obfuscation/tmpl.txt
|
||||
TARGET= ${PROG}
|
||||
#
|
||||
ALT_OBJ=
|
||||
|
||||
@@ -29,11 +29,11 @@ What happens if you do
|
||||
|
||||
## Judges' remarks:
|
||||
|
||||
Clever use of the C99 complex data type. The [deobfuscation](deobfuscation/index.html) directory
|
||||
Clever use of the C99 complex data type. The [obfuscation](obfuscation/index.html) directory
|
||||
contains clues as to how some winning authors create / edit programs into ASCII
|
||||
shapes.
|
||||
|
||||
With the source from the [deobfuscation](deobfuscation/index.html) directory could you make the code
|
||||
With the source from the [obfuscation](obfuscation/index.html) directory could you make the code
|
||||
render for a larger terminal window? How about adding more glyphs?
|
||||
|
||||
|
||||
|
||||
@@ -411,10 +411,10 @@ Location: <a href="../../location.html#JP">JP</a> - <em>Japan</em></li>
|
||||
<pre><code> ./prog prog.c</code></pre>
|
||||
<p>?</p>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>Clever use of the C99 complex data type. The <a href="deobfuscation/index.html">deobfuscation</a> directory
|
||||
<p>Clever use of the C99 complex data type. The <a href="obfuscation/index.html">obfuscation</a> directory
|
||||
contains clues as to how some winning authors create / edit programs into ASCII
|
||||
shapes.</p>
|
||||
<p>With the source from the <a href="deobfuscation/index.html">deobfuscation</a> directory could you make the code
|
||||
<p>With the source from the <a href="obfuscation/index.html">obfuscation</a> directory could you make the code
|
||||
render for a larger terminal window? How about adding more glyphs?</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<p>No! Try not. Do, or do not. There is no try.</p>
|
||||
@@ -455,20 +455,20 @@ render for a larger terminal window? How about adding more glyphs?</p>
|
||||
<li><a href="hello.txt">hello.txt</a> - sample input</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/try.sh">try.sh</a> - script to try entry</li>
|
||||
<li><a href="yoda.txt">yoda.txt</a> - sample input</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/deobfuscation/code.c">deobfuscation/code.c</a> - debofuscated code main logic</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/deobfuscation/gen.rb">deobfuscation/gen.rb</a> - ruby code to compose items and prog.c in artistic way</li>
|
||||
<li><a href="deobfuscation/glyphs.txt">deobfuscation/glyphs.txt</a> - glyphs data for deobfuscation/gen.rb</li>
|
||||
<li><a href="deobfuscation/index.html">deobfuscation/index.html</a> - deobfuscation information web page</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/deobfuscation/prog.c">deobfuscation/prog.c</a> - deobfuscated source code</li>
|
||||
<li><a href="deobfuscation/tmpl.txt">deobfuscation/tmpl.txt</a> - template for deobfuscation/gen.rb output</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/obfuscation/code.c">obfuscation/code.c</a> - debofuscated code main logic</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/obfuscation/gen.rb">obfuscation/gen.rb</a> - ruby code to compose items and prog.c in artistic way</li>
|
||||
<li><a href="obfuscation/glyphs.txt">obfuscation/glyphs.txt</a> - glyphs data for deobfuscation/gen.rb</li>
|
||||
<li><a href="obfuscation/index.html">obfuscation/index.html</a> - deobfuscation information web page</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/obfuscation/prog.c">obfuscation/prog.c</a> - deobfuscated source code</li>
|
||||
<li><a href="obfuscation/tmpl.txt">obfuscation/tmpl.txt</a> - template for deobfuscation/gen.rb output</li>
|
||||
</ul>
|
||||
<h2 id="secondary-files">Secondary files</h2>
|
||||
<ul>
|
||||
<li><a href="2020_endoh2.tar.bz2">2020_endoh2.tar.bz2</a> - download entry tarball</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/README.md">README.md</a> - markdown source for this web page</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/deobfuscation/index.md">deobfuscation/index.md</a> - markdown source for deobfuscationr/index.html</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/.entry.json">.entry.json</a> - entry summary and manifest in JSON</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/.gitignore">.gitignore</a> - list of files that should not be committed under git</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/obfuscation/index.md">obfuscation/index.md</a> - markdown source for deobfuscationr/index.html</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/.path">.path</a> - directory path from top level directory</li>
|
||||
<li><a href="index.html">index.html</a> - this web page</li>
|
||||
</ul>
|
||||
|
||||
File renamed without changes.
File renamed without changes.
File renamed without changes.
@@ -26,13 +26,13 @@
|
||||
|
||||
<!-- -->
|
||||
<!-- This web page was formed via the tool: bin/gen-other-html.sh -->
|
||||
<!-- The content of main section of this web page came from: 2020/endoh2/deobfuscation/index.md -->
|
||||
<!-- The content of main section of this web page came from: 2020/endoh2/obfuscation/index.md -->
|
||||
<!-- -->
|
||||
|
||||
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
|
||||
<!-- !!! Do not modify this web page, instead modify the file: 2020/endoh2/deobfuscation/index.md !!! -->
|
||||
<!-- !!! Do not modify this web page, instead modify the file: 2020/endoh2/deobfuscation/index.md !!! -->
|
||||
<!-- !!! Do not modify this web page, instead modify the file: 2020/endoh2/deobfuscation/index.md !!! -->
|
||||
<!-- !!! Do not modify this web page, instead modify the file: 2020/endoh2/obfuscation/index.md !!! -->
|
||||
<!-- !!! Do not modify this web page, instead modify the file: 2020/endoh2/obfuscation/index.md !!! -->
|
||||
<!-- !!! Do not modify this web page, instead modify the file: 2020/endoh2/obfuscation/index.md !!! -->
|
||||
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
|
||||
|
||||
<!-- Markdown content was converted into HTML via the tool: bin/md2html.sh -->
|
||||
@@ -371,7 +371,7 @@
|
||||
|
||||
<div class="navbar">
|
||||
<a class="Left" href="../index.html">↑ jump to index.html ↑</a>
|
||||
<a class="Right" href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2F2020%2Fendoh2%2Fdeobfuscation%2Findex.html">✓</a>
|
||||
<a class="Right" href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2F2020%2Fendoh2%2Fobfuscation%2Findex.html">✓</a>
|
||||
</div>
|
||||
|
||||
<!-- END: this line ends content from: inc/navbar.up2index.html -->
|
||||
@@ -382,19 +382,20 @@
|
||||
<!-- END: this line ends content from: inc/before-content.default.html -->
|
||||
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
|
||||
<!-- BEFORE: 1st line of markdown file: 2020/endoh2/deobfuscation/index.md -->
|
||||
<!-- BEFORE: 1st line of markdown file: 2020/endoh2/obfuscation/index.md -->
|
||||
<h1 id="opening-crawl-rot13-decoder">Opening crawl ROT13 decoder</h1>
|
||||
<p>The program contains dedicated font data for all uppercase alphabet letters.</p>
|
||||
<p>The source code of the font is <a href="glyphs.txt">glyphs.txt</a>, which is a sequence of
|
||||
chunks that is a ASCII code (65-90) followed by points data: <code>x,y,ctrl</code>.</p>
|
||||
<p>If <code>ctrl</code> is 1, the point is used as control point for quadratic bezier curve.</p>
|
||||
<p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/deobfuscation/code.c">code.c</a> is the main logic for the program, which has some placeholders
|
||||
<p>If <code>ctrl</code> is 1, the point is used as control point for quadratic <a href="https://en.wikipedia.org/wiki/Bézier_curve">bézier
|
||||
curve</a>.</p>
|
||||
<p><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/obfuscation/code.c">code.c</a> is the main logic for the program, which has some placeholders
|
||||
for font data and something.</p>
|
||||
<p>It decompresses the font data and renders a given text by projection. It
|
||||
exploits <code>C99</code>’s <code>double complex</code> type to represent 2D points, but carefully
|
||||
coded so that it does not require any <code>math.h</code> functions; you don’t have to pass
|
||||
<code>-lm</code> to <code>cc</code>.</p>
|
||||
<p><a href="tmpl.txt">tmpl.txt</a> is a template for the program. <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/deobfuscation/gen.rb">gen.rb</a> composes
|
||||
<p><a href="tmpl.txt">tmpl.txt</a> is a template for the program. <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/obfuscation/gen.rb">gen.rb</a> composes
|
||||
the all items and generates <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/endoh2/prog.c">prog.c</a>.</p>
|
||||
<hr style="width:10%;text-align:left;margin-left:0">
|
||||
<p>Jump to: <a href="#">top</a></p>
|
||||
@@ -411,7 +412,7 @@ the all items and generates <a href="https://github.com/ioccc-src/temp-test-iocc
|
||||
https://creativecommons.org/licenses/by-sa/4.0/
|
||||
|
||||
-->
|
||||
<!-- AFTER: last line of markdown file: 2020/endoh2/deobfuscation/index.md -->
|
||||
<!-- AFTER: last line of markdown file: 2020/endoh2/obfuscation/index.md -->
|
||||
|
||||
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
<!-- START: this line starts content from: inc/after-content.default.html -->
|
||||
@@ -471,7 +472,7 @@ the all items and generates <a href="https://github.com/ioccc-src/temp-test-iocc
|
||||
|
||||
<div id="coda"><h3>Coda</h3>
|
||||
<p>
|
||||
<a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2F2020%2Fendoh2%2Fdeobfuscation%2Findex.html" rel="nofollow">Nu HTML check this web page</a><br>
|
||||
<a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2F2020%2Fendoh2%2Fobfuscation%2Findex.html" rel="nofollow">Nu HTML check this web page</a><br>
|
||||
<a href="#top">Jump to top</a> <a href="#content">Jump to Content</a>
|
||||
</p>
|
||||
</div>
|
||||
@@ -5,9 +5,10 @@ The program contains dedicated font data for all uppercase alphabet letters.
|
||||
The source code of the font is [glyphs.txt](glyphs.txt), which is a sequence of
|
||||
chunks that is a ASCII code (65-90) followed by points data: `x,y,ctrl`.
|
||||
|
||||
If `ctrl` is 1, the point is used as control point for quadratic bezier curve.
|
||||
If `ctrl` is 1, the point is used as control point for quadratic [bézier
|
||||
curve](https://en.wikipedia.org/wiki/Bézier_curve).
|
||||
|
||||
[code.c](%%REPO_URL%%/2020/endoh2/deobfuscation/code.c) is the main logic for the program, which has some placeholders
|
||||
[code.c](%%REPO_URL%%/2020/endoh2/obfuscation/code.c) is the main logic for the program, which has some placeholders
|
||||
for font data and something.
|
||||
|
||||
It decompresses the font data and renders a given text by projection. It
|
||||
@@ -15,7 +16,7 @@ exploits `C99`'s `double complex` type to represent 2D points, but carefully
|
||||
coded so that it does not require any `math.h` functions; you don't have to pass
|
||||
`-lm` to `cc`.
|
||||
|
||||
[tmpl.txt](tmpl.txt) is a template for the program. [gen.rb](%%REPO_URL%%/2020/endoh2/deobfuscation/gen.rb) composes
|
||||
[tmpl.txt](tmpl.txt) is a template for the program. [gen.rb](%%REPO_URL%%/2020/endoh2/obfuscation/gen.rb) composes
|
||||
the all items and generates [prog.c](%%REPO_URL%%/2020/endoh2/prog.c).
|
||||
|
||||
|
||||
File renamed without changes.
File renamed without changes.
+12
-10
@@ -495,7 +495,7 @@ left it might be:</p>
|
||||
Please note that modifier keys like ctrl aren’t detectable or at least I’m
|
||||
unaware of how to do so.</p>
|
||||
<h2 id="modifying-the-statusscore-line-table-of-variablesstats-below">Modifying the status/score line (table of variables/stats below)</h2>
|
||||
<h3 id="deobfuscation-notice">DEOBFUSCATION NOTICE</h3>
|
||||
<h3 id="obfuscation-notice">OBFUSCATION NOTICE</h3>
|
||||
<p>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
|
||||
@@ -507,7 +507,7 @@ different sets. Please also be aware that if you don’t want any information yo
|
||||
must set it to the below at the very least; defining it without a value is not
|
||||
enough (it amounts to the parameters to a printf call):</p>
|
||||
<pre><code> #define J " " );</code></pre>
|
||||
<p>If you don’t care about brief displays of ‘o’ at 0,0 you can just have:</p>
|
||||
<p>If you don’t care about brief displays of ‘<code>o</code>’ at <code>0,0</code> you can just have:</p>
|
||||
<pre><code> #define J "");</code></pre>
|
||||
<p>That’s the bare minimum. Notice also that it’s been a long while since I’ve
|
||||
tested this part but I think this is right.</p>
|
||||
@@ -582,15 +582,17 @@ instead. Here are some ideas on how one might choose to implement something like
|
||||
this. Or maybe it’s more like what sorts of things do you have to consider and
|
||||
answer?</p>
|
||||
<ol start="0" type="1">
|
||||
<li><p>If the snake runs back into itself - thus dying - the snake would actually be
|
||||
slithering inside itself (a rather creepy thought - though they sort of do when
|
||||
they shed their skin). How then would the lives be of any value? If that would
|
||||
constitute as running into itself wouldn’t it very quickly lose all lives?</p>
|
||||
<li><p>If the snake runs back into itself - thus dying (at least without
|
||||
<code>CANNIBAL=1</code>) - the snake would actually be slithering inside itself (a rather
|
||||
creepy thought - though they sort of do when they shed their skin). How then
|
||||
would the lives be of any value? If that would constitute as running into itself
|
||||
wouldn’t it very quickly lose all lives?</p>
|
||||
<p>I can think of a number of ways to answer this question: by defining
|
||||
specific rules (as in what would be allowed and what wouldn’t be) and also
|
||||
by when to decrement the lives.</p></li>
|
||||
<li><p>If the snake hits a wall and it’s not allowed to where would the snake be
|
||||
placed? This is similar to (1) but maybe not as many things to consider.</p></li>
|
||||
<li><p>If the snake hits a wall and it’s not allowed (<code>WALLS=0</code>) to where would the
|
||||
snake be placed? This is similar to (1) but maybe not as many things to
|
||||
consider.</p></li>
|
||||
<li><p>Should the snake lose its size? WHAT does having another life even MEAN?</p></li>
|
||||
<li><p>Do you want (you do not necessarily need) a new variable that says how many
|
||||
lives you want? Either way probably be good that it can be specified by the
|
||||
@@ -626,7 +628,7 @@ snake isn’t moving which would mean the player could decide when to resume) an
|
||||
the number of bugs eaten so far. Alternatively you could have the bug simply be
|
||||
placed somewhere where the snake isn’t after replacing (can you replace
|
||||
something with itself?) the snake.</p>
|
||||
<p>Question: do you have to save the WALLS and other environmental variables?
|
||||
<p>Question: do you have to save the <code>WALLS</code> and other environmental variables?
|
||||
You wouldn’t have to but you could: if you didn’t it would mean that the player
|
||||
could change the growth size on another run for example, or they could disable
|
||||
or enable a feature.</p>
|
||||
@@ -686,7 +688,7 @@ this instead (omitting the inner if statements here):</p>
|
||||
Y=Y<2?2:*O-1;</code></pre>
|
||||
<p>Again though that’s just the idea; the code is dramatically different. The above
|
||||
incidentally is not even complete.</p>
|
||||
<p>You could also have it so depending on the WALLS value have it go through
|
||||
<p>You could also have it so depending on the <code>WALLS</code> value have it go through
|
||||
walls, end game or act as a blockade. If you really wanted you could have some
|
||||
walls you can go through and some you can’t (maybe different colours would be
|
||||
needed?).</p>
|
||||
|
||||
+12
-10
@@ -152,7 +152,7 @@ unaware of how to do so.
|
||||
|
||||
## Modifying the status/score line (table of variables/stats below)
|
||||
|
||||
### DEOBFUSCATION NOTICE
|
||||
### OBFUSCATION 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
|
||||
@@ -170,7 +170,7 @@ enough (it amounts to the parameters to a printf call):
|
||||
#define J " " );
|
||||
```
|
||||
|
||||
If you don't care about brief displays of 'o' at 0,0 you can just have:
|
||||
If you don't care about brief displays of '`o`' at `0,0` you can just have:
|
||||
|
||||
``` <!---c-->
|
||||
#define J "");
|
||||
@@ -284,17 +284,19 @@ instead. Here are some ideas on how one might choose to implement something like
|
||||
this. Or maybe it's more like what sorts of things do you have to consider and
|
||||
answer?
|
||||
|
||||
0. If the snake runs back into itself - thus dying - the snake would actually be
|
||||
slithering inside itself (a rather creepy thought - though they sort of do when
|
||||
they shed their skin). How then would the lives be of any value? If that would
|
||||
constitute as running into itself wouldn't it very quickly lose all lives?
|
||||
0. If the snake runs back into itself - thus dying (at least without
|
||||
`CANNIBAL=1`) - the snake would actually be slithering inside itself (a rather
|
||||
creepy thought - though they sort of do when they shed their skin). How then
|
||||
would the lives be of any value? If that would constitute as running into itself
|
||||
wouldn't it very quickly lose all lives?
|
||||
|
||||
I can think of a number of ways to answer this question: by defining
|
||||
specific rules (as in what would be allowed and what wouldn't be) and also
|
||||
by when to decrement the lives.
|
||||
|
||||
1. If the snake hits a wall and it's not allowed to where would the snake be
|
||||
placed? This is similar to (1) but maybe not as many things to consider.
|
||||
1. If the snake hits a wall and it's not allowed (`WALLS=0`) to where would the
|
||||
snake be placed? This is similar to (1) but maybe not as many things to
|
||||
consider.
|
||||
|
||||
2. Should the snake lose its size? WHAT does having another life even MEAN?
|
||||
|
||||
@@ -341,7 +343,7 @@ the number of bugs eaten so far. Alternatively you could have the bug simply be
|
||||
placed somewhere where the snake isn't after replacing (can you replace
|
||||
something with itself?) the snake.
|
||||
|
||||
Question: do you have to save the WALLS and other environmental variables?
|
||||
Question: do you have to save the `WALLS` and other environmental variables?
|
||||
You wouldn't have to but you could: if you didn't it would mean that the player
|
||||
could change the growth size on another run for example, or they could disable
|
||||
or enable a feature.
|
||||
@@ -423,7 +425,7 @@ this instead (omitting the inner if statements here):
|
||||
Again though that's just the idea; the code is dramatically different. The above
|
||||
incidentally is not even complete.
|
||||
|
||||
You could also have it so depending on the WALLS value have it go through
|
||||
You could also have it so depending on the `WALLS` value have it go through
|
||||
walls, end game or act as a blockade. If you really wanted you could have some
|
||||
walls you can go through and some you can't (maybe different colours would be
|
||||
needed?).
|
||||
|
||||
+1
-1
@@ -405,7 +405,7 @@ IOCCC list!</p>
|
||||
and <a href="ferguson1/index.html">Snake - 2020/ferguson1</a>.</p>
|
||||
<p>An entry, <a href="kurdyukov1/index.html">kurdyukov1</a>, pays homage to the previous entry
|
||||
<a href="../2015/hou/index.html">2015/hou</a>.</p>
|
||||
<p>…We’ll stop spouting deobfuscation information now. Have fun exploring all the entries!</p>
|
||||
<p>…We’ll stop spouting spoilers now. Have fun exploring all the entries!</p>
|
||||
<h2 id="remarks-on-some-of-submissions-that-did-not-win">Remarks on some of submissions that did not win</h2>
|
||||
<p>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
|
||||
|
||||
@@ -50,12 +50,12 @@
|
||||
"entry_text" : "encode large file C Pre-PreProcessor source"
|
||||
},
|
||||
{
|
||||
"file_path" : "deobfuscation.html",
|
||||
"file_path" : "obfuscation.html",
|
||||
"inventory_order" : 200,
|
||||
"OK_to_edit" : true,
|
||||
"display_as" : "html",
|
||||
"display_via_github" : false,
|
||||
"entry_text" : "Deobfuscation information web page"
|
||||
"entry_text" : "JavaScript page with full recording of development"
|
||||
},
|
||||
{
|
||||
"file_path" : "2020_yang.tar.bz2",
|
||||
|
||||
+2
-2
@@ -36,8 +36,8 @@ If you use the wrong code, you're gonna have a bad time.
|
||||
What is compiling this entry about?
|
||||
[Having a good .. time](https://southpark.fandom.com/wiki/Asspen/Script)!
|
||||
|
||||
This winning entry also comes with a [JavaScript timelapse
|
||||
deobfuscation](deobfuscation.html) that shows how this entry was written.
|
||||
This winning entry also comes with a [JavaScript time-lapse
|
||||
obfuscation](obfuscation.html) that shows how this entry was written.
|
||||
|
||||
|
||||
## Author's remarks:
|
||||
|
||||
@@ -416,8 +416,8 @@ generated output to make them more acceptable to typical compilers. To build:</p
|
||||
If you use the wrong code, you’re gonna have a bad time.
|
||||
What is compiling this entry about?
|
||||
<a href="https://southpark.fandom.com/wiki/Asspen/Script">Having a good .. time</a>!</p>
|
||||
<p>This winning entry also comes with a <a href="deobfuscation.html">JavaScript timelapse
|
||||
deobfuscation</a> that shows how this entry was written.</p>
|
||||
<p>This winning entry also comes with a <a href="obfuscation.html">JavaScript time-lapse
|
||||
obfuscation</a> that shows how this entry was written.</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<h3 id="synopsis">Synopsis</h3>
|
||||
<pre><code> echo "Hello world" | ./prog 12345 > encoded.c
|
||||
@@ -522,7 +522,7 @@ then compile it with a c++ compiler of your choice.</p>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/prog.orig.c">prog.orig.c</a> - original source code</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/try.sh">try.sh</a> - script to try entry</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/cppp.cc">cppp.cc</a> - encode large file C Pre-PreProcessor source</li>
|
||||
<li><a href="deobfuscation.html">deobfuscation.html</a> - Deobfuscation information web page</li>
|
||||
<li><a href="obfuscation.html">obfuscation.html</a> - JavaScript page with full recording of development</li>
|
||||
</ul>
|
||||
<h2 id="secondary-files">Secondary files</h2>
|
||||
<ul>
|
||||
|
||||
File renamed without changes.
Reference in new issue
Block a user