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
1 parent
9eb7a54e9f
commit
b0b212acb1
402 files changed
+37061
-55132
No files matched your search
+71
-102
@@ -130,8 +130,7 @@
|
||||
<h2 id="author"><a name="author"></a>Author:</h2>
|
||||
<ul>
|
||||
<li>Name: <a href="../../authors.html#Ian_Collier">Ian Collier</a><br>
|
||||
Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom
|
||||
of Great Britain and Northern Ireland</em> (<em>United Kingdom</em>)
|
||||
Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great Britain and Northern Ireland</em> (<em>United Kingdom</em>)
|
||||
<br><br></li>
|
||||
</ul>
|
||||
|
||||
@@ -151,71 +150,61 @@ of Great Britain and Northern Ireland</em> (<em>United Kingdom</em>)
|
||||
<p>To see a number of options and configurations:</p>
|
||||
<div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.sh</span></span></code></pre></div>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>The program is more interesting to run on workstations that can make
|
||||
use of a Sun raster file. Others can make use of the -text flag for
|
||||
character oriented output.</p>
|
||||
<p>The program is more interesting to run on workstations that can make use of a
|
||||
Sun raster file. Others can make use of the -text flag for character oriented
|
||||
output.</p>
|
||||
<p>Of course, the source (layout) is self-documenting! :-)</p>
|
||||
<p>NOTE: The original winning source assumed that <code>exit(3)</code>
|
||||
returned a value which cause problems for some systems where
|
||||
<code>exit(3)</code> returns a void. The file <a href="imc.c">imc.c</a>
|
||||
has been modified to avoid this problem. The original file also declared
|
||||
argc to be a <code>long</code> which was fixed.</p>
|
||||
<p>NOTE: The original winning source assumed that <code>exit(3)</code> returned a value which
|
||||
cause problems for some systems where <code>exit(3)</code> returns a void. The file
|
||||
<a href="imc.c">imc.c</a> has been modified to avoid this problem. The original file also
|
||||
declared argc to be a <code>long</code> which was fixed.</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<h3 id="portability">Portability</h3>
|
||||
<p>This program depends upon the ASCII character set, and makes certain
|
||||
assumptions about the architecture. It naughtily declares the first
|
||||
argument to <code>main()</code> as a <code>long</code>, and passes a
|
||||
pointer to <code>long</code> instead of <code>char</code> to
|
||||
<code>fwrite(3)</code>, giving a length value of 32 bytes for an array
|
||||
of 8 <code>long</code>s. I guess that makes this program OK on most
|
||||
flavours of unix, but not on PCs.</p>
|
||||
<p>This program depends upon the ASCII character set, and makes certain assumptions
|
||||
about the architecture. It naughtily declares the first argument to <code>main()</code> as
|
||||
a <code>long</code>, and passes a pointer to <code>long</code> instead of <code>char</code> to <code>fwrite(3)</code>,
|
||||
giving a length value of 32 bytes for an array of 8 <code>long</code>s. I guess that makes
|
||||
this program OK on most flavours of unix, but not on PCs.</p>
|
||||
<h3 id="about-the-program">About the program</h3>
|
||||
<p>This program has several parameters; each of them has a default, so
|
||||
the program runs happily without any parameters. If you supply an
|
||||
incorrect parameter, an obfuscated error message results! :-) Should you
|
||||
want to run the program without knowing what it does, then supplying the
|
||||
single letter <code>t</code> as a parameter is a good move. Otherwise,
|
||||
direct the output into a file. The resulting file is most useful on
|
||||
SunOS, where the <code>file(1)</code> command will tell you what to do
|
||||
with it. For best results with the <code>t</code> option, you may want
|
||||
to change the definition of the <code>I</code> macro :-) Details appear
|
||||
later, though the formatting of the code is a large clue.</p>
|
||||
<p>All the code in this program appears between the <code>;</code> and
|
||||
<code>)</code> in <code>for(;;)</code>. That isn’t because I want to win
|
||||
the best one-liner, but merely because it makes the code so much more
|
||||
impenetrable :-) In fact running a pretty printer on the code hardly
|
||||
improves it at all. This program has the obligatory macros with
|
||||
unmatched parentheses, and the cleverly arranged macro names and
|
||||
parameters to spell out <code>"Ian Colliers Obfuscated C Code"</code>.
|
||||
If you expand macros, bear in mind that the more complex ones are best
|
||||
left as macros, because they have well-defined and nontrivial (IMHO)
|
||||
functions. These macros help to give the program’s parameter format its
|
||||
flexibility. The parameters are sorted out in a unique way (based on an
|
||||
idea by Pete Bevin) which hides very effectively their identities (and I
|
||||
think that using a variable called <code>_</code> adds a nice touch to
|
||||
the illegibility of the code). In this section of the code, the data
|
||||
types of the numbers checked against is varied, and just because you see
|
||||
a <code>,</code> doesn’t mean it has anything to do with commas! So I
|
||||
hope you will agree that this program is more than a little
|
||||
obfuscated…</p>
|
||||
<p>This program has several parameters; each of them has a default, so the
|
||||
program runs happily without any parameters. If you supply an incorrect
|
||||
parameter, an obfuscated error message results! :-) Should you want to
|
||||
run the program without knowing what it does, then supplying the single
|
||||
letter <code>t</code> as a parameter is a good move. Otherwise, direct the output
|
||||
into a file. The resulting file is most useful on SunOS, where the
|
||||
<code>file(1)</code> command will tell you what to do with it. For best results with
|
||||
the <code>t</code> option, you may want to change the definition of the <code>I</code> macro :-)
|
||||
Details appear later, though the formatting of the code is a large clue.</p>
|
||||
<p>All the code in this program appears between the <code>;</code> and <code>)</code> in
|
||||
<code>for(;;)</code>. That isn’t because I want to win the best one-liner, but
|
||||
merely because it makes the code so much more impenetrable :-) In fact
|
||||
running a pretty printer on the code hardly improves it at all. This
|
||||
program has the obligatory macros with unmatched parentheses, and the
|
||||
cleverly arranged macro names and parameters to spell out <code>"Ian Colliers Obfuscated C Code"</code>. If you expand macros, bear in mind that the more
|
||||
complex ones are best left as macros, because they have well-defined and
|
||||
nontrivial (IMHO) functions. These macros help to give the program’s
|
||||
parameter format its flexibility. The parameters are sorted out in a
|
||||
unique way (based on an idea by Pete Bevin) which hides very effectively
|
||||
their identities (and I think that using a variable called <code>_</code> adds a nice
|
||||
touch to the illegibility of the code). In this section of the code, the
|
||||
data types of the numbers checked against is varied, and just because
|
||||
you see a <code>,</code> doesn’t mean it has anything to do with commas! So I hope
|
||||
you will agree that this program is more than a little obfuscated…</p>
|
||||
<p>This is a Mandelbrot/Julia drawer. Normally it produces a monochrome
|
||||
Sun-format raster file. The version of <code>xloadimage</code> we have
|
||||
is able to view such files, and so is Sun’s <code>screenload</code>
|
||||
command. [Note: the header contains eight 4-byte integers, the byte
|
||||
order in which depends upon the machine. On Sun workstations they are
|
||||
stored MSB first].</p>
|
||||
Sun-format raster file. The version of <code>xloadimage</code> we have is able to
|
||||
view such files, and so is Sun’s <code>screenload</code> command. [Note: the header
|
||||
contains eight 4-byte integers, the byte order in which depends upon the
|
||||
machine. On Sun workstations they are stored MSB first].</p>
|
||||
<p>The program may be asked to produce text output instead of a raster
|
||||
file. Then the characters defined in the <code>I</code> macro will be
|
||||
used to create up to 16 different shades of grey. Quite a respectable
|
||||
picture can be gained by printing a <code>130x110</code> output on a <a
|
||||
href="https://en.wikipedia.org/wiki/Dot_matrix_printing">dot matrix 132
|
||||
column printer</a> with the linefeed set to 7 points. Text output also
|
||||
gives a good picture when used in an X window with small characters
|
||||
having a square aspect ratio.</p>
|
||||
<p>The options accepted by the program follow. Each option is a single
|
||||
letter; it may be preceded with a minus sign (or any character in
|
||||
<code>[!-/]</code>) and may be followed by other letters, so for
|
||||
example:</p>
|
||||
file. Then the characters defined in the <code>I</code> macro will be used to create
|
||||
up to 16 different shades of grey. Quite a respectable picture can be
|
||||
gained by printing a <code>130x110</code> output on a <a href="https://en.wikipedia.org/wiki/Dot_matrix_printing">dot matrix 132 column
|
||||
printer</a> with the linefeed
|
||||
set to 7 points. Text output also gives a good picture when used in an X window
|
||||
with small characters having a square aspect ratio.</p>
|
||||
<p>The options accepted by the program follow. Each option is a single letter; it
|
||||
may be preceded with a minus sign (or any character in <code>[!-/]</code>) and may be
|
||||
followed by other letters, so for example:</p>
|
||||
<ul>
|
||||
<li>m</li>
|
||||
<li>-m</li>
|
||||
@@ -232,13 +221,12 @@ be appended to the single-letter option, so</p>
|
||||
<li>-size123 100 200</li>
|
||||
<li>s100 200</li>
|
||||
</ul>
|
||||
<p>all mean the same (note that in <code>-size123</code> all characters
|
||||
following the initial <code>s</code> are ignored). Numbers need not be
|
||||
specified, as each has a default value. In all cases except for
|
||||
<code>j</code>, <code>t</code>, and <code>s</code> whenever it appears
|
||||
before <code>t</code>, specifying an option without numbers has no
|
||||
effect. (specifying <code>-s -t</code> has the effect of producing text
|
||||
with the default raster size; not a good idea!).</p>
|
||||
<p>all mean the same (note that in <code>-size123</code> all characters following the
|
||||
initial <code>s</code> are ignored). Numbers need not be specified, as each has a
|
||||
default value. In all cases except for <code>j</code>, <code>t</code>, and <code>s</code> whenever it
|
||||
appears before <code>t</code>, specifying an option without numbers has no effect.
|
||||
(specifying <code>-s -t</code> has the effect of producing text with the default
|
||||
raster size; not a good idea!).</p>
|
||||
<h3 id="options">Options</h3>
|
||||
<p>The options of this program are:</p>
|
||||
<pre><code>-centre x y (float x,y) Centre the picture at x+iy in the complex
|
||||
@@ -261,8 +249,8 @@ with the default raster size; not a good idea!).</p>
|
||||
x=768 y=768; default for text x=63 y=23)
|
||||
|
||||
-text Produce text instead of raster.</code></pre>
|
||||
<p>The colour of each point is determined by taking the bitwise AND of
|
||||
the number of iterations and the mask. For a raster, the point is black
|
||||
<p>The colour of each point is determined by taking the bitwise AND of the
|
||||
number of iterations and the mask. For a raster, the point is black
|
||||
(1-bit) if the result is zero, white otherwise. For text, the result of
|
||||
the operation determines the greyness of the character produced, with a
|
||||
blank for zero going up to a star for the maximum value. For a
|
||||
@@ -276,53 +264,34 @@ standard error to indicate its progress (one dot per pixel line).</p>
|
||||
<p>Here are a couple of good pictures to draw:</p>
|
||||
<div class="sourceCode" id="cb5"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./imc</span> <span class="at">-s</span> 512,512 <span class="at">-f</span> 600000 <span class="at">-l</span> 512 <span class="at">-m</span> 16 <span class="at">-c.00805,.74274</span> <span class="op">></span> screen1.ras</span>
|
||||
<span id="cb5-2"><a href="#cb5-2" aria-hidden="true" tabindex="-1"></a><span class="ex">./imc</span> <span class="at">-s512,512</span> <span class="at">-j-.523,-.535</span> <span class="op">></span> screen2.ras</span></code></pre></div>
|
||||
<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>
|
||||
<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-1992imc"><a name="inventory"></a>Inventory for
|
||||
1992/imc</h1>
|
||||
<h1 id="inventory-for-1992imc"><a name="inventory"></a>Inventory for 1992/imc</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/1992/imc/imc.c">imc.c</a>
|
||||
- entry source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/Makefile">Makefile</a>
|
||||
- entry Makefile</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/imc.orig.c">imc.orig.c</a>
|
||||
- original source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/try.sh">try.sh</a>
|
||||
- how to run</li>
|
||||
<li><a href="1992_imc.tar.bz2">1992_imc.tar.bz2</a> - download entry
|
||||
source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/imc.c">imc.c</a> - entry source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/Makefile">Makefile</a> - entry Makefile</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/imc.orig.c">imc.orig.c</a> - original source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/try.sh">try.sh</a> - how to run</li>
|
||||
<li><a href="1992_imc.tar.bz2">1992_imc.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/1992/imc/.entry.json">.entry.json</a>
|
||||
- description of entry in JSON</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/.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/1992/imc/.entry.json">.entry.json</a> - description of entry in JSON</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/.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/1992/imc/README.md">README.md</a>
|
||||
- markdown source for index.html</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/imc/README.md">README.md</a> - markdown source for index.html</li>
|
||||
</ul>
|
||||
|
||||
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->
|
||||
|
||||
Reference in new issue
Block a user