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
@@ -73,7 +73,7 @@ characters as walls.
|
||||
Feed the program its own source for a default maze. Running it with no command
|
||||
line parameters will do this. In a nice symmetry, the character constant `~`
|
||||
that recognises exits to input mazes itself forms the exit to the default maze.
|
||||
Another maze, [arachnid.txt](arachnid.txt) has also been provided. This maze is
|
||||
Another maze, [arachnid.txt](%%REPO_URL%%/2004/arachnid/arachnid.txt) has also been provided. This maze is
|
||||
255x255, about the largest maze supported, for the particularly insane maze
|
||||
explorers out there.
|
||||
|
||||
|
||||
@@ -189,7 +189,7 @@ characters as walls.</p>
|
||||
<p>Feed the program its own source for a default maze. Running it with no command
|
||||
line parameters will do this. In a nice symmetry, the character constant <code>~</code>
|
||||
that recognises exits to input mazes itself forms the exit to the default maze.
|
||||
Another maze, <a href="arachnid.txt">arachnid.txt</a> has also been provided. This maze is
|
||||
Another maze, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/arachnid/arachnid.txt">arachnid.txt</a> has also been provided. This maze is
|
||||
255x255, about the largest maze supported, for the particularly insane maze
|
||||
explorers out there.</p>
|
||||
<h3 id="usage">Usage</h3>
|
||||
|
||||
@@ -62,7 +62,7 @@ of what state is being saved and restored?
|
||||
|
||||
NOTE: the author talks about how it is a single statement. This might not be
|
||||
strictly true in 2023 for the fixes for it to work so you can look at the
|
||||
original file [burley.orig.c](burley.orig.c) to see what is meant.
|
||||
original file [burley.orig.c](%%REPO_URL%%/2004/burley/burley.orig.c) to see what is meant.
|
||||
|
||||
|
||||
## Author's remarks:
|
||||
|
||||
@@ -192,7 +192,7 @@ the program so this “strategy” no longer works?</p>
|
||||
of what state is being saved and restored?</p>
|
||||
<p>NOTE: the author talks about how it is a single statement. This might not be
|
||||
strictly true in 2023 for the fixes for it to work so you can look at the
|
||||
original file <a href="burley.orig.c">burley.orig.c</a> to see what is meant.</p>
|
||||
original file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/burley/burley.orig.c">burley.orig.c</a> to see what is meant.</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<p>This program plays draw poker. What is unusual about it is that it
|
||||
is written as a single statement – count the semicolons! (OK, there
|
||||
|
||||
@@ -37,15 +37,15 @@ to not worry about writing it to a file and just viewing the image it creates.
|
||||
|
||||
## Alternate code:
|
||||
|
||||
The alt code [gavare.alt.c](gavare.alt.c) allows you to change the size of the
|
||||
The alt code [gavare.alt.c](%%REPO_URL%%/2004/gavare/gavare.alt.c) allows you to change the size of the
|
||||
image as well as the anti-alias setting, when compiling.
|
||||
|
||||
The author also provided [on their web page for the
|
||||
entry](https://gavare.se/ioccc/ioccc_gavare.c.html) an unobfuscated version that
|
||||
was used during development, which we have included in the file
|
||||
[gavare.r3.c](gavare.r3.c).
|
||||
[gavare.r3.c](%%REPO_URL%%/2004/gavare/gavare.r3.c).
|
||||
|
||||
Finally, the file [gavare.alt2.c](gavare.alt2.c) sets binary mode
|
||||
Finally, the file [gavare.alt2.c](%%REPO_URL%%/2004/gavare/gavare.alt2.c) sets binary mode
|
||||
on `stdout` which theoretically should work in Windows.
|
||||
|
||||
|
||||
|
||||
@@ -167,13 +167,13 @@ if you have ImageMagick installed, you can convert it to a jpeg:</p>
|
||||
<pre><code> ./gavare | xv -</code></pre>
|
||||
<p>to not worry about writing it to a file and just viewing the image it creates.</p>
|
||||
<h2 id="alternate-code">Alternate code:</h2>
|
||||
<p>The alt code <a href="gavare.alt.c">gavare.alt.c</a> allows you to change the size of the
|
||||
<p>The alt code <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/gavare/gavare.alt.c">gavare.alt.c</a> allows you to change the size of the
|
||||
image as well as the anti-alias setting, when compiling.</p>
|
||||
<p>The author also provided <a href="https://gavare.se/ioccc/ioccc_gavare.c.html">on their web page for the
|
||||
entry</a> an unobfuscated version that
|
||||
was used during development, which we have included in the file
|
||||
<a href="gavare.r3.c">gavare.r3.c</a>.</p>
|
||||
<p>Finally, the file <a href="gavare.alt2.c">gavare.alt2.c</a> sets binary mode
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/gavare/gavare.r3.c">gavare.r3.c</a>.</p>
|
||||
<p>Finally, the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/gavare/gavare.alt2.c">gavare.alt2.c</a> sets binary mode
|
||||
on <code>stdout</code> which theoretically should work in Windows.</p>
|
||||
<h3 id="alternate-build">Alternate build:</h3>
|
||||
<p>To build the configurable and unobfuscated versions:</p>
|
||||
|
||||
@@ -145,7 +145,7 @@ which is partially defined by the OS, and partially for the application's own
|
||||
use.
|
||||
|
||||
The program compiles into a tool to build a kernel image,
|
||||
so having built the program, the [Makefile](Makefile) will run it,
|
||||
so having built the program, the [Makefile](%%REPO_URL%%/2004/gavin/Makefile) will run it,
|
||||
redirecting the output into a file called `kernel`.
|
||||
The Makefile will then proceed to build a root filesystem image.
|
||||
This involves rebuilding the program with different compiler flags,
|
||||
|
||||
@@ -228,7 +228,7 @@ necessary work. Applications are passed a pointer to their task structure,
|
||||
which is partially defined by the OS, and partially for the application’s own
|
||||
use.</p>
|
||||
<p>The program compiles into a tool to build a kernel image,
|
||||
so having built the program, the <a href="Makefile">Makefile</a> will run it,
|
||||
so having built the program, the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/gavin/Makefile">Makefile</a> will run it,
|
||||
redirecting the output into a file called <code>kernel</code>.
|
||||
The Makefile will then proceed to build a root filesystem image.
|
||||
This involves rebuilding the program with different compiler flags,
|
||||
|
||||
@@ -26,7 +26,7 @@ we are considering starting an IOCCC standards body just to reign in the likes
|
||||
of Mr Howe.
|
||||
|
||||
This entry also has the dubious honour of being the only one to have been
|
||||
submitted with its own [configure](build/configure) script.
|
||||
submitted with its own [configure](%%REPO_URL%%/2004/hibachi/build/configure) script.
|
||||
|
||||
NOTE: the author states there is a tarball `hibachi.tgz` but this was extracted
|
||||
so the file does not exist here.
|
||||
|
||||
@@ -166,7 +166,7 @@ are not exactly sure how many organisations will be upset with this entry, but
|
||||
we are considering starting an IOCCC standards body just to reign in the likes
|
||||
of Mr Howe.</p>
|
||||
<p>This entry also has the dubious honour of being the only one to have been
|
||||
submitted with its own <a href="build/configure">configure</a> script.</p>
|
||||
submitted with its own <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/hibachi/build/configure">configure</a> script.</p>
|
||||
<p>NOTE: the author states there is a tarball <code>hibachi.tgz</code> but this was extracted
|
||||
so the file does not exist here.</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
|
||||
+1
-1
@@ -31,7 +31,7 @@ IOCCC. I thought it was time to relive hour long compile times so I made a
|
||||
program that does (almost) all computation in the pre-processor. The program
|
||||
even causes `gcc` (and other pre-processors) to crash when configured to do
|
||||
maximum number of computations. The default configuration of the
|
||||
[Makefile](Makefile) is set to make the program compile in a not too long time.
|
||||
[Makefile](%%REPO_URL%%/2004/vik2/Makefile) is set to make the program compile in a not too long time.
|
||||
|
||||
I've got `cpp` to crash in a couple of different ways. Most common is to
|
||||
get a segmentation fault, but a couple of times it just got stuck in
|
||||
|
||||
@@ -170,7 +170,7 @@ IOCCC. I thought it was time to relive hour long compile times so I made a
|
||||
program that does (almost) all computation in the pre-processor. The program
|
||||
even causes <code>gcc</code> (and other pre-processors) to crash when configured to do
|
||||
maximum number of computations. The default configuration of the
|
||||
<a href="Makefile">Makefile</a> is set to make the program compile in a not too long time.</p>
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/vik2/Makefile">Makefile</a> is set to make the program compile in a not too long time.</p>
|
||||
<p>I’ve got <code>cpp</code> to crash in a couple of different ways. Most common is to
|
||||
get a segmentation fault, but a couple of times it just got stuck in
|
||||
some infinite loop.</p>
|
||||
|
||||
Reference in new issue
Block a user