Format fixes in html files of 2014
This commit also adds the faq.html and bugs.html file that should have been committed with 2013. The reason the faq.md is updated with only the version update (backdated to yesterday) is because the version was not updated with the previous update.
This commit is contained in:
1 parent
567e6541f8
commit
8eafe398e2
11 files changed
+257
-170
No files matched your search
@@ -2843,16 +2843,17 @@ used.</li>
|
||||
<h3 id="status-inabiaf---please-do-not-fix-70">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
|
||||
<h3 id="source-code-2013endoh1endoh1.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/endoh1/endoh1.c">2013/endoh1/endoh1.c</a></h3>
|
||||
<h3 id="information-2013endoh1index.html">Information: <a href="2013/endoh1/index.html">2013/endoh1/index.html</a></h3>
|
||||
<p>From the author:</p>
|
||||
<p>–</p>
|
||||
<blockquote>
|
||||
<p>This program supports only “Combinator-calculus style notation” of Lazy K.
|
||||
“Unlambda style” and “Iota and Jot” style are not supported.</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>Also, it requires a space between identifiers. In short, use <code>(S K)</code> instead of
|
||||
<code>(SK)</code>, “`sk”, **i<em>i</em>i<em>ii</em>i<em>i</em>ii<code>, or</code>11111100011100`.</p>
|
||||
<code>(SK)</code>, “`sk”, <code>**i*i*i*ii*i*i*ii</code>, or <code>11111100011100</code>.</p>
|
||||
<p>Huge memory may be required to compile the program (about 300 MB on my machine).</p>
|
||||
<p>In addition, there are some limitations (and workarounds) mentioned in the
|
||||
<a href="2013/endoh1/index.html#obfuscation">obfuscation section</a>.</p>
|
||||
<p>–</p>
|
||||
</blockquote>
|
||||
<div id="2013_endoh3">
|
||||
<h2 id="endoh3">2013/endoh3</h2>
|
||||
</div>
|
||||
@@ -2860,12 +2861,12 @@ used.</li>
|
||||
<h3 id="source-code-2013endoh3endoh3.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/endoh3/endoh3.c">2013/endoh3/endoh3.c</a></h3>
|
||||
<h3 id="information-2013endoh3index.html">Information: <a href="2013/endoh3/index.html">2013/endoh3/index.html</a></h3>
|
||||
<p>From the author:</p>
|
||||
<p>–</p>
|
||||
<p>You can <em>NOT</em> write a note length immediately followed by a note <code>E</code>,
|
||||
such as <code>C2E2</code>.</p>
|
||||
<blockquote>
|
||||
<p>You can <em>NOT</em> write a note length immediately followed by a note <code>E</code>, such as
|
||||
<code>C2E2</code>.</p>
|
||||
<p>Can you figure out why?</p>
|
||||
<p>A workaround is inserting a whitespace: <code>C2 E2</code>.</p>
|
||||
<p>–</p>
|
||||
</blockquote>
|
||||
<div id="2013_endoh4">
|
||||
<h2 id="endoh4">2013/endoh4</h2>
|
||||
</div>
|
||||
@@ -2904,24 +2905,21 @@ it out as a known limitation it is not a bug but a feature.</p>
|
||||
<h3 id="status-inabiaf---please-do-not-fix-75">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
|
||||
<h3 id="source-code-2014maffiodo1prog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2014/maffiodo1/prog.c">2014/maffiodo1/prog.c</a></h3>
|
||||
<h3 id="information-2014maffiodo1index.html">Information: <a href="2014/maffiodo1/index.html">2014/maffiodo1/index.html</a></h3>
|
||||
<p>The author noted that in macOS the colours might be wrong. They gave a solution.
|
||||
However Cody didn’t see any problem with it and he beat the series many times.
|
||||
Of course the game here is small and he’s practically blind and it’s been a
|
||||
while since he last played so it might be wrong. Nevertheless the author does
|
||||
give a way to reconfigure the colours.</p>
|
||||
<p>The author noted that in macOS the colours might be wrong and gives a solution,
|
||||
though it is unclear if this is still true or if there was any problem at all.</p>
|
||||
<p>The author noted that the character cannot go through walls and the impression
|
||||
is that this is how it was believed but Cody ironically pointed out that there
|
||||
are known glitches where in some places you actually could go through walls.
|
||||
This might even have applied to the arcade version, Mario Bros, though that can
|
||||
no longer be confirmed by Cody. The point here is that in this game you cannot
|
||||
go through walls but it’s not a bug.</p>
|
||||
is that this is how it was believed but someone did ironically point out that
|
||||
there are known glitches where in some places you actually could go through
|
||||
walls. This might even have applied to the arcade version, Mario Bros, though
|
||||
that can no longer be confirmed by said person. The point here is that in this
|
||||
game you cannot go through walls but it’s not a bug.</p>
|
||||
<p>On the other hand, the author also stated:</p>
|
||||
<p>–</p>
|
||||
<blockquote>
|
||||
<p>When the <code>Super character</code> becomes bigger (<code>ZOOM</code> flag), the character can
|
||||
collide with blocks and get stuck inside them. This is a KNOWN BUG. When your
|
||||
player become bigger, stay away from blocks!</p>
|
||||
<p>–</p>
|
||||
<p>but since it’s documented it’s considered a feature, not a bug to fix.</p>
|
||||
</blockquote>
|
||||
<p>.. but since it’s documented it’s considered a feature, not a bug to fix.</p>
|
||||
<div id="2014_maffiodo2">
|
||||
<h2 id="maffiodo2">2014/maffiodo2</h2>
|
||||
</div>
|
||||
|
||||
Reference in new issue
Block a user