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

Finish fixing html files in 2004

Browse Source 
There is one thing brought up on GitHub that might necessitate a minor
change but that can happen later.
This commit is contained in:
Cody Boone Ferguson committed 2024-08-15 10:15:32 -07:00
1 parent ee3b035080
commit ba0f9343e1
16 files changed
+203 -139
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2004/vik1/README.md
+29 -17
View File
@@ -4,7 +4,7 @@
make
```
NOTE: this entry requires the `X11/Xlib.h` header file and the X11 library to
**NOTE**: this entry requires the `X11/Xlib.h` header file and the X11 library to
compile. For more information see the
FAQ on "[X11](../../faq.html#X11)".
@@ -86,26 +86,38 @@ Compile the source code and link X libraries if necessary.
The program takes three options which have to be typed in a specific
order as described below.
#### Usage:
``` <!---sh-->
Usage: ./vik1 ['a']['d'][#]
a - Advanced racing in a winter landscape
d - Racing in at night in the dark
# - Race track selection 1-3 are valid numbers
./vik1 ['a']['d'][#]
```
Here are a few examples:
- `a`
* Advanced racing in a winter landscape.
- `d`
* Racing in at night in the dark.
- `#`
* Race track selection 1-3 are valid numbers.
```
Command line: Description:
#### Examples:
./vik1 Run track 1 at daytime in the summer
./vik1 a Run track 1 at daytime in the winter
./vik1 d Run track 1 at night in the summer
./vik1 3 Run track 3 at daytime in the summer
./vik1 d3 Run track 3 at night in the summer
./vik1 ad2 Run track 2 at night in the winter
```
- `./vik1`
* Run track 1 at daytime in the summer.
- `./vik1 a`
* Run track 1 at daytime in the winter.
- `./vik1 d`
* Run track 1 at night in the summer.
- `./vik1 3`
* Run track 3 at daytime in the summer.
- `./vik1 d3`
* Run track 3 at night in the summer.
- `./vik1 ad2`
* Run track 2 at night in the winter.
Note that the order in which the argument characters are entered is
important. It is for example not possible to type `./vik1 da`. (Well it is
@@ -142,7 +154,7 @@ makes the program more obscure.
### Compiler warnings
There are no compiler warnings when compiling with `-ansi` but there are
many warnings from lclint. Mainly because the program is very
many warnings from lclint, mainly because the program is very
optimized for code size.
2004/vik1/index.html
+45 -16
View File
@@ -409,7 +409,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<!-- BEFORE: 1st line of markdown file: 2004/vik1/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make</code></pre>
<p>NOTE: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
<p><strong>NOTE</strong>: this entry requires the <code>X11/Xlib.h</code> header file and the X11 library to
compile. For more information see the
FAQ on “<a href="../../faq.html#X11">X11</a>”.</p>
<h2 id="to-use">To use:</h2>
@@ -454,20 +454,49 @@ glance at the feature list he provided below. Amazing!</p>
<p>Compile the source code and link X libraries if necessary.
The program takes three options which have to be typed in a specific
order as described below.</p>
<pre><code> Usage: ./vik1 [&#39;a&#39;][&#39;d&#39;][#]
a - Advanced racing in a winter landscape
d - Racing in at night in the dark
# - Race track selection 1-3 are valid numbers</code></pre>
<p>Here are a few examples:</p>
<pre><code> Command line: Description:
./vik1 Run track 1 at daytime in the summer
./vik1 a Run track 1 at daytime in the winter
./vik1 d Run track 1 at night in the summer
./vik1 3 Run track 3 at daytime in the summer
./vik1 d3 Run track 3 at night in the summer
./vik1 ad2 Run track 2 at night in the winter</code></pre>
<h4 id="usage">Usage:</h4>
<pre><code> ./vik1 [&#39;a&#39;][&#39;d&#39;][#]</code></pre>
<ul>
<li><code>a</code>
<ul>
<li>Advanced racing in a winter landscape.</li>
</ul></li>
<li><code>d</code>
<ul>
<li>Racing in at night in the dark.</li>
</ul></li>
<li><code>#</code>
<ul>
<li>Race track selection 1-3 are valid numbers.</li>
</ul></li>
</ul>
<h4 id="examples">Examples:</h4>
<ul>
<li><code>./vik1</code>
<ul>
<li>Run track 1 at daytime in the summer.</li>
</ul></li>
<li><code>./vik1 a</code>
<ul>
<li>Run track 1 at daytime in the winter.</li>
</ul></li>
<li><code>./vik1 d</code>
<ul>
<li>Run track 1 at night in the summer.</li>
</ul></li>
<li><code>./vik1 3</code>
<ul>
<li>Run track 3 at daytime in the summer.</li>
</ul></li>
<li><code>./vik1 d3</code>
<ul>
<li>Run track 3 at night in the summer.</li>
</ul></li>
<li><code>./vik1 ad2</code>
<ul>
<li>Run track 2 at night in the winter.</li>
</ul></li>
</ul>
<p>Note that the order in which the argument characters are entered is
important. It is for example not possible to type <code>./vik1 da</code>. (Well it is
possible, but the result will not be as expected.)</p>
@@ -492,7 +521,7 @@ the entry point of the application.</p>
makes the program more obscure.</p>
<h3 id="compiler-warnings">Compiler warnings</h3>
<p>There are no compiler warnings when compiling with <code>-ansi</code> but there are
many warnings from lclint. Mainly because the program is very
many warnings from lclint, mainly because the program is very
optimized for code size.</p>
<h3 id="limitations">Limitations</h3>
<p>The program only compiles and runs on X based systems.</p>