fix internal links in entry index.html from 1984 thru 2012
This commit is contained in:
1 parent
2da0a6c05f
commit
99cd17401e
151 files changed
+360
-360
No files matched your search
@@ -46,7 +46,7 @@ as the number of iterations to perform.
|
||||
|
||||
### Alternate build:
|
||||
|
||||
To use the default values, the same as [monge.c](monge.c), just do:
|
||||
To use the default values, the same as [monge.c](%%REPO_URL%%/2006/monge/monge.c), just do:
|
||||
|
||||
|
||||
``` <!---sh-->
|
||||
|
||||
@@ -171,7 +171,7 @@ of iterations to use. See <a href="#alternate-code">Alternate code</a> below.</p
|
||||
<p>This alternate code lets you specify the width and height of the image as well
|
||||
as the number of iterations to perform.</p>
|
||||
<h3 id="alternate-build">Alternate build:</h3>
|
||||
<p>To use the default values, the same as <a href="monge.c">monge.c</a>, just do:</p>
|
||||
<p>To use the default values, the same as <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/monge/monge.c">monge.c</a>, just do:</p>
|
||||
<pre><code> make alt</code></pre>
|
||||
<p>But if you wish to actually make use of it you will want to redefine one or more
|
||||
of the variables <code>W</code>, <code>H</code> and <code>I</code>. The defaults are (respectively) 400, 300 and
|
||||
|
||||
@@ -41,7 +41,7 @@ code](#original-code) was being used, you can do:
|
||||
## Original code:
|
||||
|
||||
Should you wish to see the original you may do so with the original code,
|
||||
[sloane.c](sloane.c).
|
||||
[sloane.c](%%REPO_URL%%/2006/sloane/sloane.c).
|
||||
|
||||
|
||||
### Original build:
|
||||
|
||||
@@ -173,7 +173,7 @@ code</a> was being used, you can do:</p>
|
||||
./sloane.alt</code></pre>
|
||||
<h2 id="original-code">Original code:</h2>
|
||||
<p>Should you wish to see the original you may do so with the original code,
|
||||
<a href="sloane.c">sloane.c</a>.</p>
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/sloane/sloane.c">sloane.c</a>.</p>
|
||||
<h3 id="original-build">Original build:</h3>
|
||||
<pre><code> make clobber all</code></pre>
|
||||
<h3 id="original-use">Original use:</h3>
|
||||
|
||||
@@ -119,7 +119,7 @@ The format of the input file is as follows:
|
||||
|
||||
This file describe an IFS.
|
||||
|
||||
One of the most well known would be the [Sierpinski Gasket](gasket):
|
||||
One of the most well known would be the [Sierpinski Gasket](%%REPO_URL%%/2006/stewart/gasket):
|
||||
|
||||
```
|
||||
3 0 0 1 1
|
||||
@@ -128,7 +128,7 @@ One of the most well known would be the [Sierpinski Gasket](gasket):
|
||||
.5 0 0 .5 .25 .433 .34
|
||||
```
|
||||
|
||||
or the [fern](fern):
|
||||
or the [fern](%%REPO_URL%%/2006/stewart/fern):
|
||||
|
||||
```
|
||||
4 -5.5 0 5.5 11
|
||||
|
||||
@@ -218,12 +218,12 @@ another kind of fractal, those from the <a href="https://en.wikipedia.org/wiki/I
|
||||
.
|
||||
.</code></pre>
|
||||
<p>This file describe an IFS.</p>
|
||||
<p>One of the most well known would be the <a href="gasket">Sierpinski Gasket</a>:</p>
|
||||
<p>One of the most well known would be the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/stewart/gasket">Sierpinski Gasket</a>:</p>
|
||||
<pre><code> 3 0 0 1 1
|
||||
.5 0 0 .5 0 0 .33
|
||||
.5 0 0 .5 .5 0 .33
|
||||
.5 0 0 .5 .25 .433 .34</code></pre>
|
||||
<p>or the <a href="fern">fern</a>:</p>
|
||||
<p>or the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/stewart/fern">fern</a>:</p>
|
||||
<pre><code> 4 -5.5 0 5.5 11
|
||||
0 0 0 .16 0 0 .01
|
||||
.85 .04 -.04 .85 0 1.6 .85
|
||||
|
||||
@@ -93,7 +93,7 @@ Use `sykes1.alt` as you would `sykes1` above.
|
||||
|
||||
### Alternate try:
|
||||
|
||||
The [try.sh](try.sh) script will use both versions to show some differences. You
|
||||
The [try.sh](%%REPO_URL%%/2006/sykes1/try.sh) script will use both versions to show some differences. You
|
||||
can do so like:
|
||||
|
||||
``` <!---sh-->
|
||||
@@ -103,7 +103,7 @@ can do so like:
|
||||
|
||||
## Judges' remarks:
|
||||
|
||||
Read the [sykes1.html](sykes1.html) page source.
|
||||
Read the [sykes1.html](%%REPO_URL%%/2006/sykes1/sykes1.html) page source.
|
||||
Now then read the C source. Confused? :-) If it's not clear try:
|
||||
|
||||
``` <!---sh-->
|
||||
@@ -124,7 +124,7 @@ If you did not get one for Christmas, there is an [article about these
|
||||
puzzles in wikipedia](http://en.wikipedia.org/wiki/Bedlam_cube).
|
||||
|
||||
Some instructions on how to make your own cube are in the included file
|
||||
[bedlam-cubes.pdf](bedlam-cubes.pdf).
|
||||
[bedlam-cubes.pdf](%%REPO_URL%%/2006/sykes1/bedlam-cubes.pdf).
|
||||
|
||||
Finally, you can watch it being solved with the video file here,
|
||||
[solving-bedlam-cube.mp4](solving-bedlam-cube.mp4).
|
||||
@@ -148,7 +148,7 @@ shows you how to build the cube piece by piece, rendered in glorious
|
||||
|
||||
ASCII art is all very well, but you also have a web browser, right? Well, just
|
||||
open the file [sykes1.html](sykes1.html). This html file is just a copy of
|
||||
[sykes1.c](sykes1.c), which helpfully contains an html document that should make
|
||||
[sykes1.c](%%REPO_URL%%/2006/sykes1/sykes1.c), which helpfully contains an html document that should make
|
||||
the browser display for you a nice animated GIF, showing you how to build the
|
||||
cube. Rendered in glorious 3D color.
|
||||
|
||||
|
||||
@@ -189,11 +189,11 @@ maximum:</p>
|
||||
<h3 id="alternate-use">Alternate use:</h3>
|
||||
<p>Use <code>sykes1.alt</code> as you would <code>sykes1</code> above.</p>
|
||||
<h3 id="alternate-try">Alternate try:</h3>
|
||||
<p>The <a href="try.sh">try.sh</a> script will use both versions to show some differences. You
|
||||
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/sykes1/try.sh">try.sh</a> script will use both versions to show some differences. You
|
||||
can do so like:</p>
|
||||
<pre><code> ./try.sh</code></pre>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>Read the <a href="sykes1.html">sykes1.html</a> page source.
|
||||
<p>Read the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/sykes1/sykes1.html">sykes1.html</a> page source.
|
||||
Now then read the C source. Confused? :-) If it’s not clear try:</p>
|
||||
<pre><code> diff -s sykes1.c sykes1.html</code></pre>
|
||||
<p>For extra credit, understand what happens when you give this entry
|
||||
@@ -204,7 +204,7 @@ an negative number argument, and why.</p>
|
||||
<p>If you did not get one for Christmas, there is an <a href="http://en.wikipedia.org/wiki/Bedlam_cube">article about these
|
||||
puzzles in wikipedia</a>.</p>
|
||||
<p>Some instructions on how to make your own cube are in the included file
|
||||
<a href="bedlam-cubes.pdf">bedlam-cubes.pdf</a>.</p>
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/sykes1/bedlam-cubes.pdf">bedlam-cubes.pdf</a>.</p>
|
||||
<p>Finally, you can watch it being solved with the video file here,
|
||||
<a href="solving-bedlam-cube.mp4">solving-bedlam-cube.mp4</a>.</p>
|
||||
<p>Actually the cube is very hard to do by hand by just trying to fit it
|
||||
@@ -218,7 +218,7 @@ shows you how to build the cube piece by piece, rendered in glorious
|
||||
3D ASCII.</p>
|
||||
<p>ASCII art is all very well, but you also have a web browser, right? Well, just
|
||||
open the file <a href="sykes1.html">sykes1.html</a>. This html file is just a copy of
|
||||
<a href="sykes1.c">sykes1.c</a>, which helpfully contains an html document that should make
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/sykes1/sykes1.c">sykes1.c</a>, which helpfully contains an html document that should make
|
||||
the browser display for you a nice animated GIF, showing you how to build the
|
||||
cube. Rendered in glorious 3D color.</p>
|
||||
<p>Want to see another solution? Try:</p>
|
||||
|
||||
@@ -25,15 +25,15 @@ tested with Windows. See [alternate code](#alternate-code) below.
|
||||
|
||||
## Alternate code:
|
||||
|
||||
The author provided two additional versions, [toledo3-sbar.c](toledo3-sbar.c)
|
||||
and [toledo3-txt.c](toledo3-txt.c). Respectively these create a status bar and
|
||||
The author provided two additional versions, [toledo3-sbar.c](%%REPO_URL%%/2006/toledo3/toledo3-sbar.c)
|
||||
and [toledo3-txt.c](%%REPO_URL%%/2006/toledo3/toledo3-txt.c). Respectively these create a status bar and
|
||||
make the game text only.
|
||||
|
||||
|
||||
### Alternate build:
|
||||
|
||||
With the exception of the Windows version, these are built by default. To build
|
||||
the Windows version, [toledo3.alt.c](toledo3.alt.c), you will have to figure out
|
||||
the Windows version, [toledo3.alt.c](%%REPO_URL%%/2006/toledo3/toledo3.alt.c), you will have to figure out
|
||||
how to compile Windows code.
|
||||
|
||||
|
||||
@@ -136,10 +136,10 @@ play stronger?
|
||||
|
||||
### UPGRADES
|
||||
|
||||
Using [toledo3-sbar.c](toledo3-sbar.c) (which is too large for this IOCCC size
|
||||
Using [toledo3-sbar.c](%%REPO_URL%%/2006/toledo3/toledo3-sbar.c) (which is too large for this IOCCC size
|
||||
rules) creates a status display about gameplay on the window title bar.
|
||||
|
||||
Using [toledo3-txt.c](toledo3-txt.c) turns this into being purely text based.
|
||||
Using [toledo3-txt.c](%%REPO_URL%%/2006/toledo3/toledo3-txt.c) turns this into being purely text based.
|
||||
|
||||
|
||||
<!--
|
||||
|
||||
@@ -162,12 +162,12 @@ tested with Windows. See <a href="#alternate-code">alternate code</a> below.</p>
|
||||
<h2 id="try">Try:</h2>
|
||||
<pre><code> ./toledo3 1</code></pre>
|
||||
<h2 id="alternate-code">Alternate code:</h2>
|
||||
<p>The author provided two additional versions, <a href="toledo3-sbar.c">toledo3-sbar.c</a>
|
||||
and <a href="toledo3-txt.c">toledo3-txt.c</a>. Respectively these create a status bar and
|
||||
<p>The author provided two additional versions, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/toledo3/toledo3-sbar.c">toledo3-sbar.c</a>
|
||||
and <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/toledo3/toledo3-txt.c">toledo3-txt.c</a>. Respectively these create a status bar and
|
||||
make the game text only.</p>
|
||||
<h3 id="alternate-build">Alternate build:</h3>
|
||||
<p>With the exception of the Windows version, these are built by default. To build
|
||||
the Windows version, <a href="toledo3.alt.c">toledo3.alt.c</a>, you will have to figure out
|
||||
the Windows version, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/toledo3/toledo3.alt.c">toledo3.alt.c</a>, you will have to figure out
|
||||
how to compile Windows code.</p>
|
||||
<h3 id="alternate-use">Alternate use:</h3>
|
||||
<p>Use <code>toledo3-sbar</code> and <code>toledo3-txt</code> as you would <code>toledo3</code> above.</p>
|
||||
@@ -233,9 +233,9 @@ graphical interface. Can you do it?</p>
|
||||
<p>Can the evaluation function be enhanced to make the program
|
||||
play stronger?</p>
|
||||
<h3 id="upgrades">UPGRADES</h3>
|
||||
<p>Using <a href="toledo3-sbar.c">toledo3-sbar.c</a> (which is too large for this IOCCC size
|
||||
<p>Using <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/toledo3/toledo3-sbar.c">toledo3-sbar.c</a> (which is too large for this IOCCC size
|
||||
rules) creates a status display about gameplay on the window title bar.</p>
|
||||
<p>Using <a href="toledo3-txt.c">toledo3-txt.c</a> turns this into being purely text based.</p>
|
||||
<p>Using <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2006/toledo3/toledo3-txt.c">toledo3-txt.c</a> turns this into being purely text based.</p>
|
||||
<!--
|
||||
|
||||
Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
|
||||
|
||||
Reference in new issue
Block a user