force use of pandoc version >= 3.1.12.2

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

No files matched your search

+62 -81
View File
@@ -123,121 +123,102 @@
<!-- 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="ninth-international-obfuscated-c-code-contest">Ninth
International Obfuscated C Code Contest</h1>
<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>Use <code>make</code> to compile entries. It is possible that on BSD
or non-Unix systems the Makefile needs to be changed. See the Makefile
for details.</p>
<p>Read over the Makefile for compile/build issues. Your system may
require certain changes (add or remove a library, add or remove a
<code>#define</code> i.e. the <code>-D</code> flag). A number of
compilers had problems optimizing certain entries. Some compilers do
optimize, but the resulting program does not work. By default we have
left off <code>-O</code> from compile lines. You might want to add
<code>-O</code> back, or add it back for certain entries where
performance is important. (This was updated to use <code>-O3</code> in
202n though sometimes an entry does not work if the compiler optimises
the code and in this case it is disabled or explicitly set to level
0.)</p>
<p>This year marked an all time high for number of entries as well as
the quality of entries. Nearly twice the usual number of entries made it
<h1 id="ninth-international-obfuscated-c-code-contest">Ninth International Obfuscated C Code Contest</h1>
<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>Use <code>make</code> to compile entries. It is possible that on BSD or non-Unix
systems the Makefile needs to be changed. See the Makefile for details.</p>
<p>Read over the Makefile for compile/build issues. Your system may require
certain changes (add or remove a library, add or remove a <code>#define</code> i.e. the
<code>-D</code> flag). A number of compilers had problems optimizing certain entries.
Some compilers do optimize, but the resulting program does not work. By default
we have left off <code>-O</code> from compile lines. You might want to add <code>-O</code> back, or
add it back for certain entries where performance is important. (This was
updated to use <code>-O3</code> in 202n though sometimes an entry does not work if the
compiler optimises the code and in this case it is disabled or explicitly set to
level 0.)</p>
<p>This year marked an all time high for number of entries as well as the
quality of entries. Nearly twice the usual number of entries made it
to the final judging rounds. Even when we raised the standards for
winning, we still wound up giving out a few more awards than in previous
years. The new size rules size probably contributed to the overall high
quality.</p>
years. The new size rules size probably contributed to the overall
high quality.</p>
<p>FYI: By tradition, we do not record the count of the number entries,
nor do we give our our guess as to the number of entries received. For
folks who wonder, we can say that we consumed about 2000 pages of output
(printing between 2 and 4 normal pages per side) during the judging
process this year.</p>
nor do we give our our guess as to the number of entries
received. For folks who wonder, we can say that we consumed
about 2000 pages of output (printing between 2 and 4 normal
pages per side) during the judging process this year.</p>
<p>The new instructions for submitting entries worked well - we were
able to write scripts to unpack them and eliminate duplicates.</p>
<p>As promised last year, we accepted programs that made use of the X
libraries for the first time. We now consider ANSI C compilers to be the
“standard” version that the entries were compiled with.</p>
libraries for the first time. We now consider ANSI C compilers to be
the “standard” version that the entries were compiled with.</p>
<p>Name and address information are separated from the actual program
prior to judging. This eliminates any chance that we would bias our
judging for/against any person or group. In the end, we are surprised as
you are to see who has won. Even so, it is worth noting that <a
href="../authors.html#Brian_Westley">Brian Westley</a> has submitted a
winning entry for the past 6 years!</p>
<h2 id="a-few-notes-regarding-future-contests">A few notes regarding
future contests:</h2>
judging for/against any person or group. In the end, we are surprised
as you are to see who has won. Even so, it is worth noting that
<a href="../authors.html#Brian_Westley">Brian Westley</a> has submitted
a winning entry for the past 6 years!</p>
<h2 id="a-few-notes-regarding-future-contests">A few notes regarding future contests:</h2>
<p>We did not give awards to some traditional contest categories such as
“Best Layout”. We felt that to do so would deny awards to more deserving
entries. These categories have not been eliminated. We will likely be
awarding them in future years.</p>
“Best Layout”. We felt that to do so would deny awards to more
deserving entries. These categories have not been eliminated. We will
likely be awarding them in future years.</p>
<p>We received a few entries whose instructions were rot13’d. While
nothing was said about this in the rules, we found that it made the
judging process a little harder, so we may request that this not be done
this in the future.</p>
judging process a little harder, so we may request that this not
be done this in the future.</p>
<p>Some thought has been given to a separate obfuscated perl contest.
Watch comp.lang.perl for details!</p>
<p>Be sure to wait until the 1993 rules are posted before submitting
entries. We may fine tune the rules to reflect the some ideas above.</p>
<p>Be sure to wait until the 1993 rules are posted before submitting entries.
We may fine tune the rules to reflect the some ideas above.</p>
<p>Please send us comments and suggestions what we have expressed above.
Also include anything else that you would like to see in future
contests. Send such email to:</p>
Also include anything else that you would like to see in future contests.
Send such email to:</p>
<pre><code>...!{sun,pacbell,uunet,pyramid}!hoptoad!judges
judges@toad.com</code></pre>
<p>If you use, distribute or publish these entries in some way, please
drop us a line. We enjoy seeing who, where and how the contest is
used.</p>
<p>If you use, distribute or publish these entries in some way, please drop
us a line. We enjoy seeing who, where and how the contest is used.</p>
<h2 id="final-comments">Final Comments</h2>
<p><strong>IMPORTANT NOTE</strong>: The email addresses found above are
for historical purposes only, and should not be used today. 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>: The email addresses found above are for historical
purposes only, and should not be used today. 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>
<h2 id="credits">Credits:</h2>
<p>We would like to thank Barbara Frezza for her role as official chef
of the contest. Landon Noll and Larry Bassel appreciated the opportunity
<p>We would like to thank Barbara Frezza for her role as official chef of
the contest. Landon Noll and Larry Bassel appreciated the opportunity
to serve as official taste testers. Yummo!</p>
<h1 id="copyright-and-license">Copyright and License</h1>
<p>Copyright (c) 1992,2023, Landon Curt Noll and Larry Bassel. 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) 1992,2023, Landon Curt Noll and Larry Bassel. 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-1992---the-9th-ioccc"><a name=inventory></a><a name=1992></a>Winning
Entries of 1992 - The 9th IOCCC</h1>
<p><strong>Download IOCCC</strong> <a
href="1992/ioccc.1992.tar.bz2">1992 entry source</a></p>
<h1 id="winning-entries-of-1992---the-9th-ioccc"><a name=inventory></a><a name=1992></a>Winning Entries of 1992 - The 9th IOCCC</h1>
<p><strong>Download IOCCC</strong> <a href="1992/ioccc.1992.tar.bz2">1992 entry source</a></p>
<ul>
<li><a href="adrian/index.html">1992/adrian</a> - Most Educational</li>
<li><a href="albert/index.html">1992/albert</a> - Most Useful
Program</li>
<li><a href="albert/index.html">1992/albert</a> - Most Useful Program</li>
<li><a href="ant/index.html">1992/ant</a> - Best Utility</li>
<li><a href="buzzard.1/index.html">1992/buzzard.1</a> - Most Obfuscated
Algorithm</li>
<li><a href="buzzard.2/index.html">1992/buzzard.2</a> - Best Language
Tool</li>
<li><a href="buzzard.1/index.html">1992/buzzard.1</a> - Most Obfuscated Algorithm</li>
<li><a href="buzzard.2/index.html">1992/buzzard.2</a> - Best Language Tool</li>
<li><a href="gson/index.html">1992/gson</a> - Most Humorous Output</li>
<li><a href="imc/index.html">1992/imc</a> - Best Output</li>
<li><a href="kivinen/index.html">1992/kivinen</a> - Best X Program</li>
<li><a href="lush/index.html">1992/lush</a> - Worst Abuse of the C
Preprocessor</li>
<li><a href="lush/index.html">1992/lush</a> - Worst Abuse of the C Preprocessor</li>
<li><a href="marangon/index.html">1992/marangon</a> - Best Game</li>
<li><a href="nathan/index.html">1992/nathan</a> - Worst Abuse of the
Rules</li>
<li><a href="nathan/index.html">1992/nathan</a> - Worst Abuse of the Rules</li>
<li><a href="vern/index.html">1992/vern</a> - Best of Show</li>
<li><a href="westley/index.html">1992/westley</a> - Best Small
Program</li>
<li><a href="westley/index.html">1992/westley</a> - Best Small Program</li>
</ul>
<p> <strong>Jump to:</strong> <a href="#">top</a></p>