mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

force use of pandoc version >= 3.1.12.2

Browse Source 
The `bin/pandoc-wrapper.sh` tool will verify that the ssytem
has a recent enough version of `pandoc(1)`.

We explain why we insist on `pandoc(1)`. version >= 3.1.12.2
in comments where the $PANDOC_MIN_VERSION is set.

Added `--wrap=preserve` as a default argument to `pandoc(1)`.
While this change will impact every HTML file generated,
we believe this will improve the ability of someone to look
at the generated HTML and correlate with the original markdown.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.4.2 2024-03-17"
to "1.4.3 2024-03-18".

Performed `make www` to achieve all of the above and to generate
HTML using the new  `--wrap=preserve` `pandoc(1)` mode.
This commit is contained in:
Landon Curt Noll committed 2024-03-18 01:26:39 -07:00
1 parent 9eb7a54e9f
commit b0b212acb1
402 files changed
+37061 -55132
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2020/index.html
+60 -87
View File
@@ -123,111 +123,84 @@
<!-- 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 -->
<h1 id="twenty-seventh-international-obfuscated-c-code-contest">Twenty
Seventh International Obfuscated C Code Contest</h1>
<h1 id="twenty-seventh-international-obfuscated-c-code-contest">Twenty Seventh International Obfuscated C Code Contest</h1>
<h2 id="standard-ioccc-stuff">Standard IOCCC stuff</h2>
<p>View the <code>index.html</code> web page for the given winning entry
for information on how 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>View the <code>index.html</code> web page for the given winning entry for information on how
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>
<h2 id="remarks-on-some-of-the-winning-entries">Remarks on some of the
winning entries</h2>
<p>This year’s <a href="carlini/index.html">Best of Show (carlini)</a>
is such a novel way of obfuscation that it would be worth of a special
mention in the (future) Best of IOCCC list!</p>
<p>For some reason, this year’s set of winning entries contains three
nostalgic games, <a href="tsoj/index.html">Asteroids (tsoj)</a>, <a
href="endoh1/index.html">Minesweeper (endoh1)</a>, and <a
href="ferguson1/index.html">Snake (ferguson1)</a>.</p>
<p>An entry (<a href="kurdyukov1/index.html">kurdyukov1</a>) pays homage
to previous entry <a href="2015/hou/index.htm0">2015/hou</a>.</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 on library internals or the system runtime.</p>
<p>A few entries were violating the “2053 significant bytes” rule. If an
entry could not be brought to compliance within a few seconds of looking
at the source, it was disqualified.</p>
lacking, you may need to compile using clang or gcc instead of your local
compiler.</p>
<h2 id="remarks-on-some-of-the-winning-entries">Remarks on some of the winning entries</h2>
<p>This year’s <a href="carlini/index.html">Best of Show (carlini)</a> is such a novel way of
obfuscation that it would be worth of a special mention in the (future) Best of
IOCCC list!</p>
<p>For some reason, this year’s set of winning entries contains three nostalgic games,
<a href="tsoj/index.html">Asteroids (tsoj)</a>, <a href="endoh1/index.html">Minesweeper (endoh1)</a>,
and <a href="ferguson1/index.html">Snake (ferguson1)</a>.</p>
<p>An entry (<a href="kurdyukov1/index.html">kurdyukov1</a>) pays homage to previous entry
<a href="2015/hou/index.htm0">2015/hou</a>.</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
on library internals or the system runtime.</p>
<p>A few entries were violating the “2053 significant bytes” rule. If an entry
could not be brought to compliance within a few seconds of looking at the
source, it was disqualified.</p>
<p>One entry tried to get around the size limit by putting the code into
Makefile variables and using <code>-D</code>. This is already called out
as discouraged technique in the guidelines, but it is worth a
reminder.</p>
<p>Several promising entries attempted to make use of the
<code>syscall</code> function using literal syscall numbers. This is
utterly non-portable.</p>
<p>A note to the authors: when submitting multiple entries, don’t let us
easily correlate them by coding style or documentation content, and
definitely don’t submit nearly identical versions of your program
separately. As we try to judge the entries anonymously, the similarities
will cause such entries to compete against one another, making each less
likely to win.</p>
<p>We hope the authors of non-winning entries will refine their entries
and perhaps re-submit them for the next IOCCC.</p>
Makefile variables and using <code>-D</code>. This is already called out as discouraged
technique in the guidelines, but it is worth a reminder.</p>
<p>Several promising entries attempted to make use of the <code>syscall</code> function using
literal syscall numbers. This is utterly non-portable.</p>
<p>A note to the authors: when submitting multiple entries, don’t let us easily
correlate them by coding style or documentation content, and definitely don’t
submit nearly identical versions of your program separately. As we try to judge
the entries anonymously, the similarities will cause such entries to compete
against one another, making each less likely to win.</p>
<p>We hope the authors of non-winning entries will refine their entries and
perhaps re-submit them for the next IOCCC.</p>
<h2 id="final-comments">Final Comments</h2>
<p>One more thing that feels dated is digraphs and trigraphs.</p>
<p><strong>IMPORTANT NOTE</strong>: See <a
href="../contact.html">contact.html</a> for up to date contact details
as well as details on how to provide fixes to any of the entries. See
also <a href="../faq.html">the IOCCC FAQ</a> for addition information on
the IOCCC.</p>
<p><strong>IMPORTANT NOTE</strong>: See <a href="../contact.html">contact.html</a> for up to date contact details
as well as details on how to provide fixes to any of the entries.
See also <a href="../faq.html">the IOCCC FAQ</a> for addition information on the IOCCC.</p>
<h1 id="copyright-and-license">Copyright and License</h1>
<p>Copyright (C) 2020,2023, Landon Curt Noll and Leonid A. Broukhis. All
Rights Reserved. This work is licensed under a <a
href="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons
CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0 International</a> license.
If you do use this work in some form, the <a href="../judges.html">IOCCC
judges</a> would appreciate (but does not require) if you were to <a
href="../contact.html">send us a note about your use</a>.</p>
<p>Copyright (C) 2020,2023, Landon Curt Noll and Leonid A. Broukhis. All Rights Reserved.
This work is licensed under a <a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons CC BY-SA 4.0 DEED Attribution-ShareAlike
4.0 International</a> license.
If you do use this work in some form, the <a href="../judges.html">IOCCC judges</a> would appreciate
(but does not require) if you were to <a href="../contact.html">send us a note about your use</a>.</p>
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- START: this line starts content for HTML phase 22 by: bin/output-year-index.sh via bin/md2html.sh -->
<!-- START: this line starts content generated by: bin/output-year-index.sh -->
<h1
id="winning-entries-of-2020---the-27th-ioccc"><a name=inventory></a><a name=2020></a>Winning
Entries of 2020 - The 27th IOCCC</h1>
<p><strong>Download IOCCC</strong> <a
href="2020/ioccc.2020.tar.bz2">2020 entry source</a></p>
<h1 id="winning-entries-of-2020---the-27th-ioccc"><a name=inventory></a><a name=2020></a>Winning Entries of 2020 - The 27th IOCCC</h1>
<p><strong>Download IOCCC</strong> <a href="2020/ioccc.2020.tar.bz2">2020 entry source</a></p>
<ul>
<li><a href="burton/index.html">2020/burton</a> - Best one-liner</li>
<li><a href="carlini/index.html">2020/carlini</a> - Best of show - abuse
of libc</li>
<li><a href="carlini/index.html">2020/carlini</a> - Best of show - abuse of libc</li>
<li><a href="endoh1/index.html">2020/endoh1</a> - Most explosive</li>
<li><a href="endoh2/index.html">2020/endoh2</a> - Best perspective</li>
<li><a href="endoh3/index.html">2020/endoh3</a> - Most head-turning</li>
<li><a href="ferguson1/index.html">2020/ferguson1</a> - Don’t tread on
me award</li>
<li><a href="ferguson2/index.html">2020/ferguson2</a> - Most
enigmatic</li>
<li><a href="ferguson1/index.html">2020/ferguson1</a> - Don’t tread on me award</li>
<li><a href="ferguson2/index.html">2020/ferguson2</a> - Most enigmatic</li>
<li><a href="giles/index.html">2020/giles</a> - Most phony</li>
<li><a href="kurdyukov1/index.html">2020/kurdyukov1</a> - Best
utility</li>
<li><a href="kurdyukov2/index.html">2020/kurdyukov2</a> - Least
detailed</li>
<li><a href="kurdyukov3/index.html">2020/kurdyukov3</a> - Bset slaml
prragom</li>
<li><a href="kurdyukov4/index.html">2020/kurdyukov4</a> - Best abuse of
lámatyávë</li>
<li><a href="otterness/index.html">2020/otterness</a> - Most
percussive</li>
<li><a href="tsoj/index.html">2020/tsoj</a> - Most misleading
indentation</li>
<li><a href="kurdyukov1/index.html">2020/kurdyukov1</a> - Best utility</li>
<li><a href="kurdyukov2/index.html">2020/kurdyukov2</a> - Least detailed</li>
<li><a href="kurdyukov3/index.html">2020/kurdyukov3</a> - Bset slaml prragom</li>
<li><a href="kurdyukov4/index.html">2020/kurdyukov4</a> - Best abuse of lámatyávë</li>
<li><a href="otterness/index.html">2020/otterness</a> - Most percussive</li>
<li><a href="tsoj/index.html">2020/tsoj</a> - Most misleading indentation</li>
<li><a href="yang/index.html">2020/yang</a> - Best abuse of CPP</li>
</ul>
<p> <strong>Jump to:</strong> <a href="#">top</a></p>