Fixes in html files of 1988

This commit is contained in:
Cody Boone Ferguson committed 2024-06-21 08:25:47 -07:00
1 parent a2028777b8
commit 0f66ae6dea
8 files changed
+37 -31

No files matched your search

+8 -7
View File
@@ -6,20 +6,21 @@ Look at the winning source and try to figure how it does what it does!
You may then wish to look at the Author's remarks for even more details. You may then wish to look at the Author's remarks for even more details.
The maximum size of entries was raised from 1024 to 1536 bytes, however smaller The maximum size of entries was raised from 1024 to 1536 bytes, however smaller
entries were encouraged. Due to the ["Best Abuse of the Rules" entry of entries were encouraged. Due to the [Best abuse of the rules entry of
1987](../1987/biggar/index.html), a limit of 160 chars in the compile line was introduced. 1987](../1987/biggar/index.html), a limit of 160 chars in the compile line was introduced.
This year, the Grand Prize was given to the most unusual entry and best This year, the [Best of Show](applin/index.html) was given to the most unusual
abuse of the C Preprocessor rather than the most well rounded entry. entry and the `best abuse of the C Preprocessor` rather than the most well rounded
entry.
[Rules](rules.txt) and [results](../years.html#1988) were posted to comp.lang.c, [Rules](rules.txt) and [results](../years.html#1988) were posted to _comp.lang.c_,
comp.sources.unix and alt.sources. The 1988 winning entries will be published _comp.sources.unix_ and _alt.sources_. The [1988 winning
in the [Micro/Systems entries](../years.html#1988) will be published in the [Micro/Systems
Journal](https://www.vintage-computer.com/publications.php?microsystemsjournal). Journal](https://www.vintage-computer.com/publications.php?microsystemsjournal).
Winning entries for previous years were repackaged with each year Winning entries for previous years were repackaged with each year
being in its own directory. Makefiles and hints were also provided. being in its own directory. Makefiles and hints were also provided.
The package was posted to the comp.sources.unix newsgroup. They are The package was posted to the _comp.sources.unix_ newsgroup. They are
also available on a wide number of USENET archive sites. also available on a wide number of USENET archive sites.
+3 -3
View File
@@ -40,9 +40,9 @@ Dhyrstone/sec/cpu machine) using the System V `cpp`. (The GNU `cpp` when define
`BIG_CPP` took only 45 seconds.) `BIG_CPP` took only 45 seconds.)
Your `cpp` may not be able to compile it due to a common bug that results in Your `cpp` may not be able to compile it due to a common bug that results in
`cpp` running out of space. The routine `cpp` running out of space. The alternate code
[zsmall](%%REPO_URL%%/1988/applin/applin.alt.c) is a smaller version [zsmall](%%REPO_URL%%/1988/applin/applin.alt.c) is a smaller version
of the [applin.c](%%REPO_URL%%/1988/applin/applin.c) entry. of the entry [applin.c](%%REPO_URL%%/1988/applin/applin.c).
## Judges' remarks: ## Judges' remarks:
@@ -52,7 +52,7 @@ we have received thus far. Nearly all of the real work is done in the
C preprocessor! C preprocessor!
When we compiled [applin.c](%%REPO_URL%%/1988/applin/applin.c) on an When we compiled [applin.c](%%REPO_URL%%/1988/applin/applin.c) on an
[Amdahl](https://en.wikipedia.org/wiki/Amdahl_Corporation) 5890-300E, we found that it [Amdahl 5890-300E](https://en.wikipedia.org/wiki/Amdahl_Corporation#580_series), we found that it
spent over 75 minutes in the System V C preprocessor! Besides showing that the spent over 75 minutes in the System V C preprocessor! Besides showing that the
standard System V `cpp` is slow, it showed that it contained a memory usage standard System V `cpp` is slow, it showed that it contained a memory usage
problem. The [applin.c](%%REPO_URL%%/1988/applin/applin.c) only uses 29 different preprocessor symbols problem. The [applin.c](%%REPO_URL%%/1988/applin/applin.c) only uses 29 different preprocessor symbols
+3 -3
View File
@@ -421,15 +421,15 @@ with this entry.</p>
Dhyrstone/sec/cpu machine) using the System V <code>cpp</code>. (The GNU <code>cpp</code> when defined as Dhyrstone/sec/cpu machine) using the System V <code>cpp</code>. (The GNU <code>cpp</code> when defined as
<code>BIG_CPP</code> took only 45 seconds.)</p> <code>BIG_CPP</code> took only 45 seconds.)</p>
<p>Your <code>cpp</code> may not be able to compile it due to a common bug that results in <p>Your <code>cpp</code> may not be able to compile it due to a common bug that results in
<code>cpp</code> running out of space. The routine <code>cpp</code> running out of space. The alternate code
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.alt.c">zsmall</a> is a smaller version <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.alt.c">zsmall</a> is a smaller version
of the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a> entry.</p> of the entry <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a>.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2> <h2 id="judges-remarks">Judges’ remarks:</h2>
<p>This entry is by far the most unusual abuse of the C preprocessor that <p>This entry is by far the most unusual abuse of the C preprocessor that
we have received thus far. Nearly all of the real work is done in the we have received thus far. Nearly all of the real work is done in the
C preprocessor!</p> C preprocessor!</p>
<p>When we compiled <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a> on an <p>When we compiled <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a> on an
<a href="https://en.wikipedia.org/wiki/Amdahl_Corporation">Amdahl</a> 5890-300E, we found that it <a href="https://en.wikipedia.org/wiki/Amdahl_Corporation#580_series">Amdahl 5890-300E</a>, we found that it
spent over 75 minutes in the System V C preprocessor! Besides showing that the spent over 75 minutes in the System V C preprocessor! Besides showing that the
standard System V <code>cpp</code> is slow, it showed that it contained a memory usage standard System V <code>cpp</code> is slow, it showed that it contained a memory usage
problem. The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a> only uses 29 different preprocessor symbols problem. The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/applin/applin.c">applin.c</a> only uses 29 different preprocessor symbols
+4 -4
View File
@@ -392,14 +392,14 @@ on how to compile it and how to run the winning program.
Look at the winning source and try to figure how it does what it does! Look at the winning source and try to figure how it does what it does!
You may then wish to look at the Author’s remarks for even more details.</p> You may then wish to look at the Author’s remarks for even more details.</p>
<p>The maximum size of entries was raised from 1024 to 1536 bytes, however smaller <p>The maximum size of entries was raised from 1024 to 1536 bytes, however smaller
entries were encouraged. Due to the <a href="../1987/biggar/index.html">“Best Abuse of the Rules” entry of entries were encouraged. Due to the <a href="../1987/biggar/index.html">Best abuse of the rules entry of
1987</a>, a limit of 160 chars in the compile line was introduced.</p> 1987</a>, a limit of 160 chars in the compile line was introduced.</p>
<p>This year, the <a href="applin/index.html">Best of Show</a> was given to the most unusual <p>This year, the <a href="applin/index.html">Best of Show</a> was given to the most unusual
entry and <code>best abuse of the C Preprocessor</code> rather than the most well rounded entry and the <code>best abuse of the C Preprocessor</code> rather than the most well rounded
entry.</p> entry.</p>
<p><a href="rules.txt">Rules</a> and <a href="../years.html#1988">results</a> were posted to <em>comp.lang.c</em>, <p><a href="rules.txt">Rules</a> and <a href="../years.html#1988">results</a> were posted to <em>comp.lang.c</em>,
<em>comp.sources.unix</em> and <em>alt.sources</em>. The 1988 winning entries will be published <em>comp.sources.unix</em> and <em>alt.sources</em>. The <a href="../years.html#1988">1988 winning
in the <a href="https://www.vintage-computer.com/publications.php?microsystemsjournal">Micro/Systems entries</a> will be published in the <a href="https://www.vintage-computer.com/publications.php?microsystemsjournal">Micro/Systems
Journal</a>.</p> Journal</a>.</p>
<p>Winning entries for previous years were repackaged with each year <p>Winning entries for previous years were repackaged with each year
being in its own directory. Makefiles and hints were also provided. being in its own directory. Makefiles and hints were also provided.
+3 -4
View File
@@ -69,10 +69,9 @@ from a single macro (e.g., `"O/**/O"` creates either `++` or `--` by defining
NOTE: Most System V machines were not be able to execute this program correctly NOTE: Most System V machines were not be able to execute this program correctly
due to the fact that BSD style systems have an `sprintf(3)` that returns a `char due to the fact that BSD style systems have an `sprintf(3)` that returns a `char
*`. Due to the above problems, we placed the output of this program in the *`. Due to the above problems, we placed the output of this program in the
file [isaak.output.txt](isaak.output.txt). file [isaak.output.txt](isaak.output.txt). Since this was fixed, this file is
not strictly necessary, but we keep it for historical purposes (decoded as it
Since this was fixed, this file is not strictly necessary, but we keep it for used to be uuencoded). See the
historical purposes (decoded as it used to be uuencoded). See the
[isaak.orig.c](%%REPO_URL%%/1988/isaak/isaak.orig.c) for the original source. [isaak.orig.c](%%REPO_URL%%/1988/isaak/isaak.orig.c) for the original source.
FYI: We are likely to be more strict about portability in the future. FYI: We are likely to be more strict about portability in the future.
+3 -3
View File
@@ -437,9 +437,9 @@ from a single macro (e.g., <code>"O/**/O"</code> creates either <code>++</code>
<code>O</code> to be <code>+</code> or <code>-</code>) may cause some strict ANSI C preprocessors to object.</p> <code>O</code> to be <code>+</code> or <code>-</code>) may cause some strict ANSI C preprocessors to object.</p>
<p>NOTE: Most System V machines were not be able to execute this program correctly <p>NOTE: Most System V machines were not be able to execute this program correctly
due to the fact that BSD style systems have an <code>sprintf(3)</code> that returns a <code>char *</code>. Due to the above problems, we placed the output of this program in the due to the fact that BSD style systems have an <code>sprintf(3)</code> that returns a <code>char *</code>. Due to the above problems, we placed the output of this program in the
file <a href="isaak.output.txt">isaak.output.txt</a>.</p> file <a href="isaak.output.txt">isaak.output.txt</a>. Since this was fixed, this file is
<p>Since this was fixed, this file is not strictly necessary, but we keep it for not strictly necessary, but we keep it for historical purposes (decoded as it
historical purposes (decoded as it used to be uuencoded). See the used to be uuencoded). See the
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/isaak/isaak.orig.c">isaak.orig.c</a> for the original source.</p> <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/isaak/isaak.orig.c">isaak.orig.c</a> for the original source.</p>
<p>FYI: We are likely to be more strict about portability in the future.</p> <p>FYI: We are likely to be more strict about portability in the future.</p>
<h2 id="authors-remarks">Author’s remarks:</h2> <h2 id="authors-remarks">Author’s remarks:</h2>
+6 -3
View File
@@ -60,19 +60,22 @@ Your compiler must parse
as `--a` and not `-(-a)` or some other tokenized form. Some strictly as `--a` and not `-(-a)` or some other tokenized form. Some strictly
conforming ANSI C Preprocessors may object to this: for such conforming ANSI C Preprocessors may object to this: for such
compilers, you can elide the non-standard token-pasting requirement compilers, you can elide the non-standard token-pasting requirement
by changing the #define line to: by changing the `#define` line to:
``` <!---c--> ``` <!---c-->
#define _ F-->00||F-OO--; #define _ F-->00||F-OO--;
``` ```
This is what the modified code in [westley.c](%%REPO_URL%%/1988/westley/westley.c) does whereas the alt This is what the modified code in
code is the original. [westley.c](%%REPO_URL%%/1988/westley/westley.c) does whereas the alternate code
is the original.
You might enjoy looking at the output of: You might enjoy looking at the output of:
``` <!---sh--> ``` <!---sh-->
cc -E westley.alt.c cc -E westley.alt.c
cc -E westley.c
``` ```
+7 -4
View File
@@ -427,12 +427,15 @@ try:</p>
<p>as <code>--a</code> and not <code>-(-a)</code> or some other tokenized form. Some strictly <p>as <code>--a</code> and not <code>-(-a)</code> or some other tokenized form. Some strictly
conforming ANSI C Preprocessors may object to this: for such conforming ANSI C Preprocessors may object to this: for such
compilers, you can elide the non-standard token-pasting requirement compilers, you can elide the non-standard token-pasting requirement
by changing the #define line to:</p> by changing the <code>#define</code> line to:</p>
<pre><code> #define _ F--&gt;00||F-OO--;</code></pre> <pre><code> #define _ F--&gt;00||F-OO--;</code></pre>
<p>This is what the modified code in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/westley/westley.c">westley.c</a> does whereas the alt <p>This is what the modified code in
code is the original.</p> <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1988/westley/westley.c">westley.c</a> does whereas the alternate code
is the original.</p>
<p>You might enjoy looking at the output of:</p> <p>You might enjoy looking at the output of:</p>
<pre><code> cc -E westley.alt.c</code></pre> <pre><code> cc -E westley.alt.c
cc -E westley.c</code></pre>
<h2 id="authors-remarks">Author’s remarks:</h2> <h2 id="authors-remarks">Author’s remarks:</h2>
<p>No remarks were provided by the author.</p> <p>No remarks were provided by the author.</p>
<!-- <!--