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

2000/dlowe/index.html
+106 -143
View File
@@ -129,9 +129,9 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#J_David_Lowe">J. David
Lowe</a><br> Location: <a href="../../location.html#US">US</a> -
<em>United States of America</em> (<em>United States</em>) <br><br></li>
<li>Name: <a href="../../authors.html#J_David_Lowe">J. David Lowe</a><br>
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -148,8 +148,7 @@ Lowe</a><br> Location: <a href="../../location.html#US">US</a> -
<p>The current status of this entry is:</p>
<pre><code>STATUS: doesn&#39;t work with some platforms - please help us fix
STATUS: known bug - please help us fix</code></pre>
<p>For more detailed information see <a
href="../../bugs.html#2000_dlowe">2000 dlowe bugs</a>.</p>
<p>For more detailed information see <a href="../../bugs.html#2000_dlowe">2000 dlowe bugs</a>.</p>
<h2 id="to-use">To use:</h2>
<div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./dlowe</span> [file ...]</span></code></pre></div>
<h2 id="try">Try:</h2>
@@ -159,27 +158,23 @@ href="../../bugs.html#2000_dlowe">2000 dlowe bugs</a>.</p>
the use of embedded language interpreters. The judges considered
disqualifying this entry because of the use of perl, but on the other
hand it qualifies as the Worst Abuse of the Rules. As a previous author,
<a href="../../authors.html#J_David_Lowe">David Lowe</a> continues to
inflict the highest quality “poot” on the Judges.</p>
<p>The program also contains an undocumented command for Chad and Chongo
(Landon). The judges’ remarks contain a clue to the hidden command
:-).</p>
<a href="../../authors.html#J_David_Lowe">David Lowe</a> continues to inflict the highest quality “poot” on the
Judges.</p>
<p>The program also contains an undocumented command for Chad and Chongo (Landon).
The judges’ remarks contain a clue to the hidden command :-).</p>
<ul>
<li>The IOCCC uses an anonymous judging process which keeps the identity
of the submitters hidden until all winning entries have been
selected.</li>
of the submitters hidden until all winning entries have been selected.</li>
</ul>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="usage">Usage</h3>
<pre><code>./dlowe [file ...]</code></pre>
<h3 id="synopsis">Synopsis</h3>
<p>This is a <a
href="https://en.wikipedia.org/wiki/Reverse_Polish_notation">Reverse
Polish calculator</a>, loosely based on the <code>dc(1)</code> unix
calculator.</p>
<p>This is a <a href="https://en.wikipedia.org/wiki/Reverse_Polish_notation">Reverse Polish
calculator</a>, loosely
based on the <code>dc(1)</code> unix calculator.</p>
<h1 id="syntax">Syntax</h1>
<p>This program understands the following <code>dc(1)</code>
commands:</p>
<p>This program understands the following <code>dc(1)</code> commands:</p>
<pre><code>p prints the top stack value without altering the stack.
P prints the top stack value, removing it from the stack, and
doesn&#39;t print a trailing newline.
@@ -200,14 +195,13 @@ r reverses the order of the top two stack values.</code></pre>
% Pops 2 values and pushes the remainder of the division that
/ would do.</code></pre>
<p>The precision and range are double, like it or not, except that the
modulus operator actually returns <code>(p1 - (p2 * (p1 / p2)))</code>,
but with the innermost division calculated at integer precision. This is
usually what you expect
(e.g. <code>echo "12 8 % p" | ./dlowe == 4</code>)</p>
<p>Commands are read from <code>stdin</code> or from a list of files
named on the command line. Unlike <code>dc(1)</code>, multiple commands
on the same line must be space separated. Commands are only executed
when a newline or EOF is encountered.</p>
modulus operator actually returns <code>(p1 - (p2 * (p1 / p2)))</code>, but with
the innermost division calculated at integer precision. This is
usually what you expect (e.g. <code>echo "12 8 % p" | ./dlowe == 4</code>)</p>
<p>Commands are read from <code>stdin</code> or from a list of files named on
the command line. Unlike <code>dc(1)</code>, multiple commands on the same line
must be space separated. Commands are only executed when a newline
or EOF is encountered.</p>
<h3 id="diagnostics">Diagnostics:</h3>
<pre><code>&quot;stack empty&quot; Not enough on the stack for the requested command
&quot;divide by zero&quot; Attempt to divide by zero
@@ -218,8 +212,7 @@ Floating point exception (core dumped) (or something to that effect)
This bug appears to be fixed in perl5.6.0
</code></pre>
<h3 id="examples">Examples:</h3>
<div class="sourceCode" id="cb10"><pre
class="sourceCode sh"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" aria-hidden="true" tabindex="-1"></a><span class="ex">$</span> echo <span class="st">&#39;12 13 14 15 16 + + + + f&#39;</span> <span class="kw">|</span> <span class="ex">./dlowe</span></span>
<div class="sourceCode" id="cb10"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" aria-hidden="true" tabindex="-1"></a><span class="ex">$</span> echo <span class="st">&#39;12 13 14 15 16 + + + + f&#39;</span> <span class="kw">|</span> <span class="ex">./dlowe</span></span>
<span id="cb10-2"><a href="#cb10-2" aria-hidden="true" tabindex="-1"></a><span class="ex">70</span></span>
<span id="cb10-3"><a href="#cb10-3" aria-hidden="true" tabindex="-1"></a><span class="ex">$</span> echo <span class="st">&#39;12 13 14 15 16 17 + - * / p&#39;</span> <span class="kw">|</span> <span class="ex">./dlowe</span></span>
<span id="cb10-4"><a href="#cb10-4" aria-hidden="true" tabindex="-1"></a><span class="ex">-0.0515873015873016</span></span>
@@ -234,174 +227,144 @@ class="sourceCode sh"><code class="sourceCode bash"><span id="cb10-1"><a href="#
<span id="cb10-13"><a href="#cb10-13" aria-hidden="true" tabindex="-1"></a><span class="ex">$</span> echo <span class="st">&#39;7 P 6 d P P 8 p&#39;</span> <span class="kw">|</span> <span class="ex">./dlowe</span> <span class="kw">|</span> <span class="fu">tr</span> 876 tpo</span>
<span id="cb10-14"><a href="#cb10-14" aria-hidden="true" tabindex="-1"></a><span class="ex">poot</span></span></code></pre></div>
<h3 id="code-concept">Code Concept:</h3>
<p>We all know that Perl and other VHLLs (very high level languages) are
particularly well-suited for (among other things) string handling, I/O,
and powerful built-in data types, and (relatively) poorly suited for
number crunching and other processor-intensive tasks - areas where C is
strongest. This program takes this knowledge to its extreme conclusion,
using each language for its strengths. Thus, it uses Perl to read and
parse input, for output, and for the easy-to-use list primitive, and
uses C for mathematical operations. Since the rules of this contest
state that the program must be generated by an ANSI C compiler, of
course, the outer Perl layer is wrapped with a thin layer of C.</p>
<p>We all know that Perl and other VHLLs (very high level languages)
are particularly well-suited for (among other things) string
handling, I/O, and powerful built-in data types, and (relatively)
poorly suited for number crunching and other processor-intensive
tasks - areas where C is strongest. This program takes this
knowledge to its extreme conclusion, using each language for its
strengths. Thus, it uses Perl to read and parse input, for output,
and for the easy-to-use list primitive, and uses C for mathematical
operations. Since the rules of this contest state that the program
must be generated by an ANSI C compiler, of course, the outer Perl
layer is wrapped with a thin layer of C.</p>
<p>In case that wasn’t clear, in a nutshell: this program is C, calling
embedded Perl (contained in a C string), which in turn calls back to C,
which performs math on Perl data types and calls Perl functions for
embedded Perl (contained in a C string), which in turn calls back to
C, which performs math on Perl data types and calls Perl functions for
error reporting.</p>
<h3 id="requirements">Requirements:</h3>
<p>Unfortunately, Perl is an evolving beast - that includes the
embedding API and the XS API. The code was developed under
<code>Perl 5.005_03</code>, successfully tested against
<code>Perl 5.6.0</code>, <code>Perl 5.005_02</code> and
<code>Perl 5.004_04</code>, and according to the version delta
documentation, should work as-is with <code>Perl 5.002</code> and later
(which has been around since February 1996). To clarify - it’s not the
Perl code itself that may be non-portable, it’s the C code for embedding
Perl and for calling C from Perl.</p>
<code>Perl 5.005_03</code>, successfully tested against <code>Perl 5.6.0</code>, <code>Perl 5.005_02</code>
and <code>Perl 5.004_04</code>, and according to the version delta documentation,
should work as-is with <code>Perl 5.002</code> and later (which has been around
since February 1996). To clarify - it’s not the Perl code itself
that may be non-portable, it’s the C code for embedding Perl and for
calling C from Perl.</p>
<p>It is also important that Perl be installed cleanly and correctly.
You may have problems linking if, for example, you have multiple
overlapping versions of Perl installed (which might not be a problem for
scripts, but causes problems with embedding the interpreter). More
commonly, you may get non-fatal warnings from the linker, caused by
slight mis-configurations of Perl on your system.</p>
<p>Some compilers also complain that “third argument of
<code>main()</code> is deprecated” or something to that effect. But in
Perl prior to <code>5.6.0</code>, the header file “proto.h” actually had
a prototype for <code>main()</code>, so applications which embed Perl
must use the three argument form of <code>main()</code>.</p>
overlapping versions of Perl installed (which might not be a problem
for scripts, but causes problems with embedding the interpreter).
More commonly, you may get non-fatal warnings from the linker, caused
by slight mis-configurations of Perl on your system.</p>
<p>Some compilers also complain that “third argument of <code>main()</code> is
deprecated” or something to that effect. But in Perl prior to
<code>5.6.0</code>, the header file “proto.h” actually had a prototype for <code>main()</code>, so
applications which embed Perl must use the three argument form of <code>main()</code>.</p>
<h3 id="aside-history">Aside: history…</h3>
<p>Larry Wall wrote the original Perl in 1986-87, the same two
successive years he won the IOCCC. I hope this program helps you to
realize that this was no fluke - that Perl and Obfuscation are as
inseparable as, say, camels and humps.</p>
<p>Larry Wall wrote the original Perl in 1986-87, the same two successive
years he won the IOCCC. I hope this program helps you to realize that
this was no fluke - that Perl and Obfuscation are as inseparable as,
say, camels and humps.</p>
<h3 id="obfuscated">Obfuscated?</h3>
<ul>
<li><p>Reverse Polish notation is pretty strange, in and of
itself.</p></li>
<li><p>Reverse Polish notation is pretty strange, in and of itself.</p></li>
<li><p>The layout of the program is three roughly symmetrical “stacks”
of code. This layout is quite sensitive in places - my C indenter
actually breaks the code by inserting spaces in certain places.</p></li>
<li><p>Anyone who has ever programmed in Perl can attest to the fact
that it is particularly well-suited to obfuscation; thus, the Perl is
<li><p>Anyone who has ever programmed in Perl can attest to the fact that
it is particularly well-suited to obfuscation; thus, the Perl is
obfuscated. (Here’s my favorite legal Perl from this program:
<code>_:$_=&lt;&gt;;</code> - but <code>$SS[$#SS]-=$SS[$#SS-1]</code>
isn’t bad, either).</p></li>
<code>_:$_=&lt;&gt;;</code> - but <code>$SS[$#SS]-=$SS[$#SS-1]</code> isn’t bad, either).</p></li>
<li><p>I’ve eschewed traditional branch and loop structures such as
<code>if</code> and <code>for</code>, in favor of their oft-neglected
cousins, <code>goto</code> and <code>?:</code>, in both the Perl and C
code.</p></li>
<code>if</code> and <code>for</code>, in favor of their oft-neglected cousins, <code>goto</code>
and <code>?:</code>, in both the Perl and C code.</p></li>
<li><p>I’ve used some highly magical Perl incantations, such as symbolic
references, the <code>goto &amp;NAME</code> syntax,
<code>AUTOLOAD</code> for exception handling, and abuse of the default
scalar (<code>$_</code>).</p></li>
references, the <code>goto &amp;NAME</code> syntax, <code>AUTOLOAD</code> for exception handling,
and abuse of the default scalar (<code>$_</code>).</p></li>
<li><p>I’ve also deliberately used Perl syntax that is very much unlike
C syntax: the <code>&amp;NAME</code> rather than <code>NAME()</code>
function calling syntax, leaving off parentheses wherever possible,
using <code>print()</code> instead of <code>printf()</code>, and using
the English style logic operators <code>and</code> and <code>or</code>
rather than <code>&amp;&amp;</code> and <code>||</code>, for
example.</p></li>
C syntax: the <code>&amp;NAME</code> rather than <code>NAME()</code> function calling syntax,
leaving off parentheses wherever possible, using <code>print()</code> instead
of <code>printf()</code>, and using the English style logic operators <code>and</code> and
<code>or</code> rather than <code>&amp;&amp;</code> and <code>||</code>, for example.</p></li>
<li><p>The fact that all the Perl code is in double-quotes doesn’t lend
any readability to the regular expressions and quoted strings
therein.</p></li>
<li><p>The points and ways in which C and Perl connect are
<em>really</em> obscure. They’re also incredibly poorly documented, as
they’re primarily used in machine-generated code. However, there’s a
wealth of example code on <a href="https://www.cpan.org">CPAN
(www.cpan.org)</a>.</p></li>
<li><p>The Perl API functions are almost all macros, so you will
probably find that preprocessor expansion will only make things worse.
They also have helpful, verbose names like <code>SvNV</code>,
<code>SvIV</code>, and <code>newSVpv</code>. I couldn’t have done better
myself!</p></li>
<li><p>The points and ways in which C and Perl connect are <em>really</em>
obscure. They’re also incredibly poorly documented, as they’re
primarily used in machine-generated code. However, there’s a
wealth of example code on <a href="https://www.cpan.org">CPAN (www.cpan.org)</a>.</p></li>
<li><p>The Perl API functions are almost all macros, so you will probably
find that preprocessor expansion will only make things worse. They
also have helpful, verbose names like <code>SvNV</code>, <code>SvIV</code>, and <code>newSVpv</code>. I
couldn’t have done better myself!</p></li>
<li><p>Figuring out how the mathematical C functions get called is a bit
tricky. Note the lack of explicit switching based on command
input.</p></li>
<li><p>Because of the “interesting” way that commands are interpreted,
all of the commands have synonyms. For example, if you find it easier to
remember, <code>=</code> is synonymous with <code>d</code>. This also
makes it possible to write (even more) obfuscated reverse Polish
commands (I figure this explanation moves the synonyms from ‘bug’ to
all of the commands have synonyms. For example, if you find it
easier to remember, <code>=</code> is synonymous with <code>d</code>. This also makes it
possible to write (even more) obfuscated reverse Polish commands
(I figure this explanation moves the synonyms from ‘bug’ to
‘feature’!)</p></li>
</ul>
<p>. The first IOCCC entry with an “easter egg”?…</p>
<h3 id="aside-on-unobfuscated-perl">Aside: on unobfuscated Perl</h3>
<p>My original intent was to write obfuscated C and crystal-clear Perl,
to highlight my bending of the rules. Unfortunately, Perl really doesn’t
lend itself to crystal-clear code…</p>
to highlight my bending of the rules. Unfortunately, Perl really
doesn’t lend itself to crystal-clear code…</p>
<h3 id="bending-the-rules">Bending the rules?</h3>
<p>Well, the rules never state that you can’t embed another programming
language, but on the other hand, knowing Perl probably isn’t high on the
list of qualifications for judges… Oh dear, I guess your C beautifier
won’t help too much, either ;)</p>
language, but on the other hand, knowing Perl probably isn’t high on
the list of qualifications for judges… Oh dear, I guess your C
beautifier won’t help too much, either ;)</p>
<p>If you don’t change the rules, it’ll be embedded Ada next year!</p>
<h3 id="auto-defend">Auto defend</h3>
<p>A. Isn’t this the obfuscated C contest? What’s this Perl
<code>$#_&amp;&amp;$_</code>?</p>
<p>D. Hey, this program <em>is</em> 100% C, and does not exec an
external Perl interpreter. It simply links against the Perl language
library. The “Perl code” is just a C string constant.</p>
<p>A. Isn’t this the obfuscated C contest? What’s this Perl <code>$#_&amp;&amp;$_</code>?</p>
<p>D. Hey, this program <em>is</em> 100% C, and does not exec an external Perl
interpreter. It simply links against the Perl language library.
The “Perl code” is just a C string constant.</p>
<p>A. Perl isn’t portable enough, or ubiquitous enough.</p>
<p>D. I’d argue that it is more portable than X. According to the Perl
folks, it runs on the following platforms: Acorn, AIX, Amiga, AS/400,
BeOS, Concurrent, Debian, DEC OSF/1, Digital UNIX, EPOC, FreeBSD,
Guardian, HP-UX, IRIX, LinuxPPC, LynxOS, MacOS, MachTen, Minix, MPE/iX,
MS-DOS, MVS, NetBSD, Netware, NextStep, OpenBSD, OpenLinux, ODT,
OpenVMS, OS/2, OS390, OSR, PowerMAX, Psion, QNX, Redhat, Reliant UNIX,
RISCOS, SCO, SGI, SINIX, Slackware, Solaris, Sun, SuSE, Tandem, Tru64,
UNIX, U/WIN, Unixware, VMS, Win31, Win32, Windows 3.1, and Windows
95/98/NT/2K. Granted, embeddable Perl isn’t quite so portable, but
still…</p>
<p>Also, Perl 5 is bundled with the following OS distributions: AIX
4.3.3+, FreeBSD 3.0+, IRIX 6.4+, every Linux distribution, NetBSD,
OpenBSD, and DEC Tru64 5.0+, again according to the Perl people.</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0
License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights
Reserved. You are free to share and adapt this file under the terms of
this license:</p>
MS-DOS, MVS, NetBSD, Netware, NextStep, OpenBSD, OpenLinux, ODT, OpenVMS,
OS/2, OS390, OSR, PowerMAX, Psion, QNX, Redhat, Reliant UNIX, RISCOS,
SCO, SGI, SINIX, Slackware, Solaris, Sun, SuSE, Tandem, Tru64, UNIX,
U/WIN, Unixware, VMS, Win31, Win32, Windows 3.1, and Windows 95/98/NT/2K.
Granted, embeddable Perl isn’t quite so portable, but still…</p>
<p>Also, Perl 5 is bundled with the following OS distributions: AIX 4.3.3+,
FreeBSD 3.0+, IRIX 6.4+, every Linux distribution, NetBSD, OpenBSD, and
DEC Tru64 5.0+, again according to the Perl people.</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0 License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved.
You are free to share and adapt this file under the terms of this license:</p>
<pre><code>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</code></pre>
<p>For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/</p>
<p>For more information, see: https://creativecommons.org/licenses/by-sa/4.0/</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-index-inventory.sh via bin/md2html.sh -->
<!-- START: this line starts content generated by: bin/output-index-inventory.sh -->
<h1 id="inventory-for-2000dlowe"><a name="inventory"></a>Inventory for
2000/dlowe</h1>
<h1 id="inventory-for-2000dlowe"><a name="inventory"></a>Inventory for 2000/dlowe</h1>
<p><a href="#top">Jump to top</a></p>
<h2 id="primary-files">Primary files</h2>
<ul>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/dlowe.c">dlowe.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/dlowe.orig.c">dlowe.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/try.sh">try.sh</a>
- how to run</li>
<li><a href="2000_dlowe.tar.bz2">2000_dlowe.tar.bz2</a> - download entry
source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/dlowe.c">dlowe.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/dlowe.orig.c">dlowe.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/try.sh">try.sh</a> - how to run</li>
<li><a href="2000_dlowe.tar.bz2">2000_dlowe.tar.bz2</a> - download entry source</li>
</ul>
<h2 id="secondary-files">Secondary files</h2>
<ul>
<li><a href="index.html">index.html</a> - entry home page</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/.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/2000/dlowe/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/.gitignore">.gitignore</a> - list of files that should not be committed under git</li>
<li><a href=".path">.path</a> - directory path from top directory</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dlowe/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->