fix many internal links
Fixed a number of internal links that need to go to the GitHub site. Ran `make www` to perform the above.
This commit is contained in:
1 parent
b84f8cbe28
commit
e7d69bc232
175 files changed
+645
-631
No files matched your search
@@ -333,7 +333,7 @@ rate in which the terminal application receives and displays the [ANSI
|
||||
escape](https://en.wikipedia.org/wiki/ANSI_escape_code) sequences.
|
||||
|
||||
To slow down the output programmatically, introduce a delay immediately after the
|
||||
call to `fflush(3)` (N.B: see [birken.alt.c](birken.alt.c)).
|
||||
call to `fflush(3)` (N.B: see [birken.alt.c](%%REPO_URL%%/2013/birken/birken.alt.c)).
|
||||
|
||||
|
||||
### IOCCC Size Tool Bug
|
||||
|
||||
@@ -600,7 +600,7 @@ represented using ANSI escape sequences.</p>
|
||||
rate in which the terminal application receives and displays the <a href="https://en.wikipedia.org/wiki/ANSI_escape_code">ANSI
|
||||
escape</a> sequences.</p>
|
||||
<p>To slow down the output programmatically, introduce a delay immediately after the
|
||||
call to <code>fflush(3)</code> (N.B: see <a href="birken.alt.c">birken.alt.c</a>).</p>
|
||||
call to <code>fflush(3)</code> (N.B: see <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/birken/birken.alt.c">birken.alt.c</a>).</p>
|
||||
<h3 id="ioccc-size-tool-bug">IOCCC Size Tool Bug</h3>
|
||||
<p>This program demonstrates how to exploit a bug in IOCCC size tool version
|
||||
<code>2013-07-30-v17</code>. The first line of the program is reproduced below.</p>
|
||||
|
||||
@@ -112,7 +112,7 @@ little endian machine.
|
||||
|
||||
### RULE 2 ABUSE DISCLAIMER
|
||||
|
||||
- [cable3.c](cable3.c) is 4043 bytes in length (half an 8086).
|
||||
- [cable3.c](%%REPO_URL%%/2013/cable3/cable3.c) is 4043 bytes in length (half an 8086).
|
||||
- `iocccsize -i < cable3.c` returns 1977 (the year the 4.77 MHz 8086 CPU was announced)
|
||||
- Therefore, any suspicions the judges may have regarding rule 2 non-compliance
|
||||
might be well-intentioned but are groundless.
|
||||
|
||||
@@ -445,7 +445,7 @@ and somewhat useless beast. For everyone else, please run the emulator on a
|
||||
little endian machine.</p>
|
||||
<h3 id="rule-2-abuse-disclaimer">RULE 2 ABUSE DISCLAIMER</h3>
|
||||
<ul>
|
||||
<li><a href="cable3.c">cable3.c</a> is 4043 bytes in length (half an 8086).</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/cable3/cable3.c">cable3.c</a> is 4043 bytes in length (half an 8086).</li>
|
||||
<li><code>iocccsize -i < cable3.c</code> returns 1977 (the year the 4.77 MHz 8086 CPU was announced)</li>
|
||||
<li>Therefore, any suspicions the judges may have regarding rule 2 non-compliance
|
||||
might be well-intentioned but are groundless.</li>
|
||||
|
||||
@@ -88,7 +88,7 @@ and with Apple clang version 15.0.0 (clang-1500.0.40.1) in 2023, we get:
|
||||
|
||||
Which one is correct? :)
|
||||
|
||||
NOTE: `make all` will compile [fun.c](fun.c) but to provide a different compiler
|
||||
NOTE: `make all` will compile [fun.c](%%REPO_URL%%/2013/dlowe/fun.c) but to provide a different compiler
|
||||
you can do something like:
|
||||
|
||||
``` <!---sh-->
|
||||
@@ -113,13 +113,13 @@ A tiny implementation of command-line
|
||||
sparkline of file sizes: ▁▁▁▃▃▂▁▂▁▁▉
|
||||
```
|
||||
|
||||
NOTE: this has been provided in [slflen.sh](slflen.sh) so you can try:
|
||||
NOTE: this has been provided in [slflen.sh](%%REPO_URL%%/2013/dlowe/slflen.sh) so you can try:
|
||||
|
||||
``` <!---sh-->
|
||||
./slflen.sh
|
||||
```
|
||||
|
||||
instead (which [try.sh](try.sh) also uses).
|
||||
instead (which [try.sh](%%REPO_URL%%/2013/dlowe/try.sh) also uses).
|
||||
|
||||
|
||||
### Description
|
||||
|
||||
@@ -413,7 +413,7 @@ with one argument or when all arguments are equal?</p>
|
||||
<p>and with Apple clang version 15.0.0 (clang-1500.0.40.1) in 2023, we get:</p>
|
||||
<pre><code> 1840985120 -2033041452 35979112</code></pre>
|
||||
<p>Which one is correct? :)</p>
|
||||
<p>NOTE: <code>make all</code> will compile <a href="fun.c">fun.c</a> but to provide a different compiler
|
||||
<p>NOTE: <code>make all</code> will compile <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/dlowe/fun.c">fun.c</a> but to provide a different compiler
|
||||
you can do something like:</p>
|
||||
<pre><code> make CC=clang fun</code></pre>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
@@ -426,9 +426,9 @@ you can do something like:</p>
|
||||
|
||||
$ echo "sparkline of file lengths: $(wc -c * | awk '{print $1}' | xargs ./sparkl)"
|
||||
sparkline of file sizes: ▁▁▁▃▃▂▁▂▁▁▉</code></pre>
|
||||
<p>NOTE: this has been provided in <a href="slflen.sh">slflen.sh</a> so you can try:</p>
|
||||
<p>NOTE: this has been provided in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/dlowe/slflen.sh">slflen.sh</a> so you can try:</p>
|
||||
<pre><code> ./slflen.sh</code></pre>
|
||||
<p>instead (which <a href="try.sh">try.sh</a> also uses).</p>
|
||||
<p>instead (which <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/dlowe/try.sh">try.sh</a> also uses).</p>
|
||||
<h3 id="description">Description</h3>
|
||||
<p>This is a handy little tool for visualizing numeric series from the
|
||||
command line, using sparklines. Pass it a numeric series as arguments, and
|
||||
|
||||
@@ -142,7 +142,7 @@ So, try:
|
||||
./endoh4 < endoh4.c # or ./endoh4.sh
|
||||
```
|
||||
|
||||
The [solids/](solids/) directory includes various solid data:
|
||||
The `solids` directory includes various solid data:
|
||||
|
||||
- [Platonic solids](http://en.wikipedia.org/wiki/Platonic_solid)
|
||||
- [Archimedean solids](http://en.wikipedia.org/wiki/Archimedean_solid)
|
||||
|
||||
@@ -451,7 +451,7 @@ clang, and tcc. It should not trigger warnings with <code>-pedantic</code> and <
|
||||
<p>The shape of this code is the geometric net of a regular tetrahedron.
|
||||
So, try:</p>
|
||||
<pre><code> ./endoh4 < endoh4.c # or ./endoh4.sh</code></pre>
|
||||
<p>The <a href="solids/">solids/</a> directory includes various solid data:</p>
|
||||
<p>The <code>solids</code> directory includes various solid data:</p>
|
||||
<ul>
|
||||
<li><a href="http://en.wikipedia.org/wiki/Platonic_solid">Platonic solids</a></li>
|
||||
<li><a href="http://en.wikipedia.org/wiki/Archimedean_solid">Archimedean solids</a></li>
|
||||
|
||||
+2
-2
@@ -1,4 +1,4 @@
|
||||
## To build:
|
||||
%%REPO_URL%%/## To build:
|
||||
|
||||
``` <!---sh-->
|
||||
make all
|
||||
@@ -137,7 +137,7 @@ don't have to worry about conflicts.
|
||||
* [hou.c](%%REPO_URL%%/2013/hou/hou.c) uses compression to get around the size limit. The compression
|
||||
fully complies with the rules and the guidelines (at least the portion that
|
||||
shows up in `grep` "size limit"). Please see the [Self-imposed
|
||||
restrictions](self-imposed-restrictions) section below for more details.
|
||||
restrictions](#self-imposed-restrictions) section below for more details.
|
||||
* `hou` does not terminate (as suggested by the second line of rule 6).
|
||||
|
||||
|
||||
|
||||
@@ -587,7 +587,7 @@ editing program, you need to convert the RGB values from 0..255 to 0..1, and
|
||||
then put here its <em>square</em>. Only after squaring you get your real, lively color
|
||||
in the output image, as opposed to something dull and gray. You need to do the
|
||||
same if you use a RGB texture. And yes, that is the what the second <code>sqrt(3)</code> in
|
||||
<a href="../a.c">a.c</a> is for.</p>
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/hou/a.c">a.c</a> is for.</p>
|
||||
<p>Going beyond colors, to define a shiny or dull surface one needs more maths, and
|
||||
optics. The jargon for this is <code>BRDF</code> (Bidirectional Reflectance Distribution
|
||||
Function) importance sampling. Let’s continue to function <code>o</code>.</p>
|
||||
|
||||
@@ -312,7 +312,7 @@ editing program, you need to convert the RGB values from 0..255 to 0..1, and
|
||||
then put here its *square*. Only after squaring you get your real, lively color
|
||||
in the output image, as opposed to something dull and gray. You need to do the
|
||||
same if you use a RGB texture. And yes, that is the what the second `sqrt(3)` in
|
||||
[a.c](../a.c) is for.
|
||||
[a.c](%%REPO_URL%%/2013/hou/a.c) is for.
|
||||
|
||||
Going beyond colors, to define a shiny or dull surface one needs more maths, and
|
||||
optics. The jargon for this is `BRDF` (Bidirectional Reflectance Distribution
|
||||
|
||||
+2
-2
@@ -377,7 +377,7 @@ Location: <a href="../../location.html#CN">CN</a> - <em>People’s Republic of C
|
||||
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
|
||||
<!-- BEFORE: 1st line of markdown file: 2013/hou/README.md -->
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<p>https://github.com/ioccc-src/temp-test-ioccc/blob/master/## To build:</p>
|
||||
<pre><code> make all</code></pre>
|
||||
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
|
||||
<p>The current status of this entry is:</p>
|
||||
@@ -468,7 +468,7 @@ don’t have to worry about conflicts.</li>
|
||||
<ul>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2013/hou/hou.c">hou.c</a> uses compression to get around the size limit. The compression
|
||||
fully complies with the rules and the guidelines (at least the portion that
|
||||
shows up in <code>grep</code> “size limit”). Please see the <a href="self-imposed-restrictions">Self-imposed
|
||||
shows up in <code>grep</code> “size limit”). Please see the <a href="#self-imposed-restrictions">Self-imposed
|
||||
restrictions</a> section below for more details.</li>
|
||||
<li><code>hou</code> does not terminate (as suggested by the second line of rule 6).</li>
|
||||
</ul>
|
||||
|
||||
Reference in new issue
Block a user