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

2011/toledo/index.html
+100 -136
View File
@@ -129,9 +129,9 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Oscar_Toledo">Oscar Toledo
G.</a><br> Location: <a href="../../location.html#MX">MX</a> -
<em>United Mexican States</em> (<em>Mexico</em>) <br><br></li>
<li>Name: <a href="../../authors.html#Oscar_Toledo">Oscar Toledo G.</a><br>
Location: <a href="../../location.html#MX">MX</a> - <em>United Mexican States</em> (<em>Mexico</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -142,26 +142,22 @@ G.</a><br> Location: <a href="../../location.html#MX">MX</a> -
<h2 id="to-build">To build:</h2>
<p>If you have X11 installed:</p>
<div class="sourceCode" id="cb1"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span></span></code></pre></div>
<p>There are two alternate versions, <a href="toledo.alt.c">one that
lets you reconfigure the controls and size</a> and <a
href="toledo.alt2.c">another that should work for Windows</a>. See <a
href="#alternate-code">Alternate code</a> below.</p>
<p>There are two alternate versions, <a href="toledo.alt.c">one that lets you reconfigure the
controls and size</a> and <a href="toledo.alt2.c">another that should work for
Windows</a>. See <a href="#alternate-code">Alternate code</a> below.</p>
<h2 id="to-use">To use:</h2>
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./toledo</span></span></code></pre></div>
<h2 id="alternate-code">Alternate code:</h2>
<p>The first alt version, <a href="toledo.alt.c">toledo.alt.c</a>,
allows you to reconfigure the controls and the dimensions more
easily.</p>
<p>The second version, <a href="toledo.alt2.c">toledo.alt2.c</a>, should
work for Windows but does not allow you to reconfigure the keys or
dimensions. This is because it cannot be tested by us.</p>
<p>The first alt version, <a href="toledo.alt.c">toledo.alt.c</a>, allows you to reconfigure
the controls and the dimensions more easily.</p>
<p>The second version, <a href="toledo.alt2.c">toledo.alt2.c</a>, should work for Windows but
does not allow you to reconfigure the keys or dimensions. This is because it
cannot be tested by us.</p>
<h3 id="alternate-build">Alternate build:</h3>
<p>For the one that lets you reconfigure the keys you will want to look
at the included header file, <a href="keysym.h">keysym.h</a>, to find
the correct macros. Once you have the right names you can define the
macros <code>FIRE</code>, <code>FORWARD</code>, <code>BACKWARD</code>,
<code>LEFT</code>, <code>RIGHT</code>, <code>WIDTH</code> and
<code>HEIGHT</code>. Here are the defaults:</p>
<p>For the one that lets you reconfigure the keys you will want to look at the
included header file, <a href="keysym.h">keysym.h</a>, to find the correct macros. Once you
have the right names you can define the macros <code>FIRE</code>, <code>FORWARD</code>, <code>BACKWARD</code>,
<code>LEFT</code>, <code>RIGHT</code>, <code>WIDTH</code> and <code>HEIGHT</code>. Here are the defaults:</p>
<pre><code>FIRE= XK_BackSpace:XK_Tab
FORWARD= XK_Up:XK_w
BACKWARD= XK_Down:XK_s
@@ -169,26 +165,24 @@ LEFT= XK_Left:XK_a
RIGHT= XK_Right:XK_d
WIDTH= 512
HEIGHT= 288</code></pre>
<p>but you can change them about however you like, even with other keys.
For instance to swap <code>LEFT</code> and <code>RIGHT</code>:</p>
<p>but you can change them about however you like, even with other keys. For
instance to swap <code>LEFT</code> and <code>RIGHT</code>:</p>
<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="fu">make</span> clobber LEFT=XK_Right:XK_d RIGHT=XK_Left:XK_a alt</span></code></pre></div>
<p>but you can specify something completely else and you can pick and
choose which controls you wish to redefine. You might also wish to
change the dimensions of the game, <code>WIDTH</code> and
<code>HEIGHT</code> which have an arbitrarily selected lower limit as
<p>but you can specify something completely else and you can pick and choose which
controls you wish to redefine. You might also wish to change the dimensions of
the game, <code>WIDTH</code> and <code>HEIGHT</code> which have an arbitrarily selected lower limit as
well as the default values.</p>
<p>Observe that each of the controls are a pair in the form of
<code>player2:player1</code> (yes, player 2 comes first!).</p>
<p>Observe that each of the controls are a pair in the form of <code>player2:player1</code>
(yes, player 2 comes first!).</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>This two player game uses X11. The control keys can be configured by
modifying the <code>A</code>, <code>B</code>, <code>C</code>,
<code>D</code> and <code>E</code> macros at compilation.</p>
<p>After a quick splash screen the objective should be clear. There are
Red, Green and Cyan tanks. A larger window can be made by altering the
source early on, right before the code gets hard to follow, or using the
modifying the <code>A</code>, <code>B</code>, <code>C</code>, <code>D</code> and <code>E</code> macros at compilation.</p>
<p>After a quick splash screen the objective should be clear. There
are Red, Green and Cyan tanks. A larger window can be made by altering
the source early on, right before the code gets hard to follow, or using the
<a href="#alternate-code">alternate version</a>.</p>
<p>Like Oscar’s previous winning X11 program for the 19th IOCCC, if you
remove both the X11 include files and replace them with</p>
<p>Like Oscar’s previous winning X11 program for the 19th IOCCC, if
you remove both the X11 include files and replace them with</p>
<div class="sourceCode" id="cb5"><pre class="sourceCode c"><code class="sourceCode c"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="pp">#include </span><span class="im">&quot;layer.c&quot;</span></span></code></pre></div>
<p>you ought to be able to compile and run this program on Windows.
NOTE: this is what <a href="toledo.alt2.c">toledo.alt2.c</a> is for.</p>
@@ -200,24 +194,25 @@ NOTE: this is what <a href="toledo.alt2.c">toledo.alt2.c</a> is for.</p>
|| || //===| || || ||=// \\=\\ ==/ |=/
|| || || || || || || \\ || User&#39;s
\===/ \\==// || || || \\ \==// Manual</code></pre>
<p>This is a color X11 3D tank-game for two players, just compile and
run it without arguments.</p>
<p>This is a color X11 3D tank-game for two players, just compile
and run it without arguments.</p>
<p>You will see briefly a tank spinning before each level.</p>
<p>The Left half of the window shows the red player view and the right
half shows the green player view; the background will change to blue
when the view goes inactive.</p>
<p>The objective is to chase and destroy the other player’s tank. There
is also an aqua tank for testing your aim and getting extra points.</p>
half shows the green player view; the background will change to
blue when the view goes inactive.</p>
<p>The objective is to chase and destroy the other player’s tank.
There is also an aqua tank for testing your aim and getting
extra points.</p>
<p>Caveat: You can shoot only 3 bullets at a time.<br />
Trick: You can fire faster if they explode on anything.<br />
Believe it or not, it has strategy!</p>
<p>When only one tank remains on the field, the level will advance.
Don’t forget to destroy the aqua tank.</p>
<p>The <strike>battle</strike>playground is surrounded by mountains and
each level is filled with random obstacles (pyramids and cubes).</p>
<p>The bars show players energy and score; each bar shows energy and
indicates the current player view (wider on the left). The right part
grows with every point.</p>
<p>The <strike>battle</strike>playground is surrounded by mountains and each level is
filled with random obstacles (pyramids and cubes).</p>
<p>The bars show players energy and score; each bar shows energy
and indicates the current player view (wider on the left). The right
part grows with every point.</p>
<p>Keys for player 1 (lowercase):</p>
<ul>
<li>Tab - Fire</li>
@@ -238,8 +233,8 @@ grows with every point.</p>
<p>If you don’t like the keys assignment, you can change it in the
Makefile or use the <a href="#alternate-code">alternate version</a>.</p>
<h3 id="parental-advisory-warning">PARENTAL ADVISORY WARNING:</h3>
<p>This game is highly violent: when the tank explodes you can see the
little stick man blowing in parts.</p>
<p>This game is highly violent: when the tank explodes you can
see the little stick man blowing in parts.</p>
<p>Not really, just kidding :D</p>
<h3 id="platforms-tested">PLATFORMS TESTED:</h3>
<ul>
@@ -262,30 +257,26 @@ little stick man blowing in parts.</p>
<li>Animated intro.</li>
<li>It has color!</li>
</ul>
<h3 id="features-that-programmers-will-find-appealing">FEATURES THAT
PROGRAMMERS WILL FIND APPEALING:</h3>
<h3 id="features-that-programmers-will-find-appealing">FEATURES THAT PROGRAMMERS WILL FIND APPEALING:</h3>
<ul>
<li>Works both with 32 and 64-bit CPUs.</li>
<li>Double buffered, portable to any X11 with 24/32-bit color.</li>
<li>Memory-hungry as must be any 3D program; uses a 256 MB array.</li>
<li>Total and absolute irreverent coding style, so it generates a lot of
warnings when compiled.</li>
<li>It can take several minutes to compile (known culprits: Fedora Core
11-14 on x86-64 512 MB).</li>
<li>Total and absolute irreverent coding style, so it generates a lot of warnings
when compiled.</li>
<li>It can take several minutes to compile (known culprits: Fedora Core 11-14 on
x86-64 512 MB).</li>
<li>It is written in the only true C: K&amp;R, and no, that doesn’t mean
Katherine &amp; Rose.</li>
<li>Vectorial scalable graphics: do you want a bigger viewport? Change
variables <code>M</code> and <code>N</code> (see the <a
href="#alternate-code">alternate code</a>).</li>
<li>Half of the program is formatted as 3D cube. View with tabs at 8
columns and a square font.</li>
<li>The other half of the program is unprintable source code, so no
typing from paper, you have to write a converter of tabs and form-feeds
to its C escaped forms.</li>
<li>No text, so this program can be used and understood easily in any
country.</li>
<li>This program is highly ecological, it sleeps when it is not doing
anything.</li>
<li>Vectorial scalable graphics: do you want a bigger viewport? Change variables
<code>M</code> and <code>N</code> (see the <a href="#alternate-code">alternate code</a>).</li>
<li>Half of the program is formatted as 3D cube. View with tabs at 8 columns and a
square font.</li>
<li>The other half of the program is unprintable source code, so no typing from
paper, you have to write a converter of tabs and form-feeds to its C escaped
forms.</li>
<li>No text, so this program can be used and understood easily in any country.</li>
<li>This program is highly ecological, it sleeps when it is not doing anything.</li>
<li>Virtual world with its own physics laws.</li>
<li>When closing the window it will show an X11 error :P</li>
</ul>
@@ -295,8 +286,7 @@ anything.</li>
<li>Function arguments used as variables.</li>
<li>Operators used freely.</li>
<li>Pre-calculated values to save bytes.</li>
<li>Uses the <code>+++</code>, <code>+-</code> and <code>*+</code>
undocumented C operators :P</li>
<li>Uses the <code>+++</code>, <code>+-</code> and <code>*+</code> undocumented C operators :P</li>
</ul>
<pre><code>
....,,,,---++++++--,,..\
@@ -321,27 +311,26 @@ undocumented C operators :P</li>
.,-+++++,@@==
</code></pre>
<h3 id="the-history-of-this-program">THE HISTORY OF THIS PROGRAM:</h3>
<p>When I started working on this program, I figured that it would be
easy to fit on the character limit, but I missed three things: the
enormous X11 names, the non-portable key codes and my 2 KB of
artwork.</p>
<p>Very hard coding did the first thing. In fact I worked out
twenty-nine different versions and at one step I had four parallel
versions with different characteristics removed (mountains, horizon
lines, score/status bars and explosions) but I’ve managed to fit it all
together!</p>
<p>The second thing was solved using the Makefile: it is under 160 bytes
and you get adjustable controls. The greatest mystery on the Earth is
why X11 gives non-portable key codes to the user.</p>
<p>And finally, the third “Thing” was growing and growing, and growing,
eating bytes for lunch… after endless rounds of crunching I obtained
three-hundred seventy-eight bytes of artwork and guess what? It doesn’t
fit.</p>
<p>So I had to integrate a decompressor based on the space, tabulators
and other non-counted characters.</p>
<p>The final program is composed of eight micro-functions: one is the
core and does most of the hard work and the other functions help do the
X11 things, explosion effects, 3D calculations and viewing.</p>
<p>When I started working on this program, I figured that it would
be easy to fit on the character limit, but I missed three things: the enormous
X11 names, the non-portable key codes and my 2 KB of artwork.</p>
<p>Very hard coding did the first thing. In fact I worked out twenty-nine different
versions and at one step I had four parallel versions with different
characteristics removed (mountains, horizon lines, score/status bars and
explosions) but I’ve managed to fit it all together!</p>
<p>The second thing was solved using the Makefile: it is under
160 bytes and you get adjustable controls. The greatest
mystery on the Earth is why X11 gives non-portable key codes to
the user.</p>
<p>And finally, the third “Thing” was growing and growing, and
growing, eating bytes for lunch… after endless rounds of
crunching I obtained three-hundred seventy-eight bytes of
artwork and guess what? It doesn’t fit.</p>
<p>So I had to integrate a decompressor based on the space, tabulators and other
non-counted characters.</p>
<p>The final program is composed of eight micro-functions: one is the core and does
most of the hard work and the other functions help do the X11 things, explosion
effects, 3D calculations and viewing.</p>
<ul>
<li><code>K()</code> - 3D transformation</li>
<li><code>s()</code> - Rendering</li>
@@ -350,71 +339,46 @@ X11 things, explosion effects, 3D calculations and viewing.</p>
<li><code>g()</code> - Moves 3D object backward and forward</li>
<li><code>F()</code> - Collision detection</li>
<li><code>T()</code> - Core (also known as main loop :D)</li>
<li><code>main()</code> - Initialization and ‘uncruncher’, what a common
name!; C programs should start in the cool() function :).</li>
<li><code>main()</code> - Initialization and ‘uncruncher’, what a common name!;
C programs should start in the cool() function :).</li>
</ul>
<p>The source code was formatted as a cube using a specially written
program. This program is smaller and obfuscated what is needed so the
reformatting doesn’t exceeded the character limits. The crunched vectors
were generated by another special program and the tank that surrounds
this text was generated by yet another program.</p>
<p>The source code was formatted as a cube using a specially written program. This
program is smaller and obfuscated what is needed so the reformatting doesn’t
exceeded the character limits. The crunched vectors were generated by another
special program and the tank that surrounds this text was generated by yet
another program.</p>
<p><em>Have fun!</em></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>
<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-2011toledo"><a name="inventory"></a>Inventory for
2011/toledo</h1>
<h1 id="inventory-for-2011toledo"><a name="inventory"></a>Inventory for 2011/toledo</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/2011/toledo/toledo.c">toledo.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.alt.c">toledo.alt.c</a>
- alternative source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.alt2.c">toledo.alt2.c</a>
- alternate alternative source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.orig.c">toledo.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/keysym.h">keysym.h</a>
- included header file</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/layer.c">layer.c</a>
- translation layer to make 3D Tanks game</li>
<li><a href="2011_toledo.tar.bz2">2011_toledo.tar.bz2</a> - download
entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.c">toledo.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.alt.c">toledo.alt.c</a> - alternative source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.alt2.c">toledo.alt2.c</a> - alternate alternative source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/toledo.orig.c">toledo.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/keysym.h">keysym.h</a> - included header file</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/layer.c">layer.c</a> - translation layer to make 3D Tanks game</li>
<li><a href="2011_toledo.tar.bz2">2011_toledo.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/2011/toledo/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/.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/2011/toledo/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/.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/2011/toledo/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/toledo/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->