Format, typo, consistency check YYYY/README.md
There are many fixes made but a few questions remain so when I reach those years I will address those then. Unfortunately, due to infrastructure work right now, this is all I can say even though there are a number of things I'd like to say.
This commit is contained in:
1 parent
778f57b318
commit
ffdd724032
47 files changed
+326
-556
No files matched your search
+7
-10
@@ -392,20 +392,15 @@
|
||||
on how to compile it and how to run the winning program.
|
||||
Look at the winning source and try to figure how it does what it does!
|
||||
You may then wish to look at the Author’s remarks for even more details.</p>
|
||||
<p>The primary site can be found at <a href="https://www.ioccc.org">www.ioccc.org</a>.</p>
|
||||
<p>Use <code>make</code> to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the Makefile needs to be changed. See the Makefile for details.</p>
|
||||
<p>Read over the Makefile and index.html files for compile/build issues. Your
|
||||
system may require certain changes (add or remove a library, add or remove a
|
||||
<code>#define</code>).</p>
|
||||
<p>Some C compilers are not quite as good as they should be. If yours is
|
||||
lacking, you may need to compile using clang or gcc instead of your local
|
||||
compiler.</p>
|
||||
<p>The primary website can be found at <a href="https://www.ioccc.org">www.ioccc.org</a>.</p>
|
||||
<h2 id="remarks-on-some-of-the-winning-entries">Remarks on some of the winning entries</h2>
|
||||
<p>This year’s winning entries are impressive!</p>
|
||||
<p>The <a href="endoh/index.html">Most in need of debugging - 2019/endoh</a> is very inventive in
|
||||
a way it produces its own text!</p>
|
||||
<p>The <a href="ciura/index.html">Most likely to be awarded - 2019/ciura</a> has an amazing
|
||||
<p>The <a href="ciura/index.html">Most alphabetic- 2019/ciura</a> has an amazing
|
||||
vocabulary!</p>
|
||||
<p>There are again nods to entries of the years:</p>
|
||||
<ul>
|
||||
@@ -413,9 +408,11 @@ vocabulary!</p>
|
||||
<li><a href="../2011/blakely/index.html">2011/blakely</a></li>
|
||||
</ul>
|
||||
<p>These nods to not run afoul of the guideline:</p>
|
||||
<pre><code> We tend to dislike programs that:
|
||||
...
|
||||
are rather similar to previous entries</code></pre>
|
||||
<blockquote>
|
||||
<p>We tend to dislike programs that:
|
||||
…
|
||||
are rather similar to previous entries</p>
|
||||
</blockquote>
|
||||
<p>because the entry <a href="dogon/index.html">2019/dogon</a> appropriately pays homage
|
||||
to past entries without blatantly reusing their code.</p>
|
||||
<p>…We’ll stop spouting spoilers now. Have fun exploring all the entries!</p>
|
||||
|
||||
Reference in new issue
Block a user