Get all 1988 entries to compile

For 1988/dale it will not compile under macOS. I was able to get it to
almost compile under macOS but there was one problem. As well this 'fix'
will make it not compile under linux. One change was required which was
changing the #define _ define followed by #_ foo to be just '#define
foo' etc.

Added to 1988/isaak/.gitignore isaak.output.

1988/spinellis won't compile with clang.

1988/phillipps will compile but it is likely to segfault at least in
some systems (maybe not all).

Updated many README.md files for the changes above (and probably other
changes I've neglected to write in this log). Most changes in the readme
files are probably just formatting and probably typos as well as how to
compile and run entries nowadays. There might have been other changes.
This commit is contained in:
Cody Boone Ferguson committed 2023-03-05 09:39:48 -08:00
1 parent 923a1f46d0
commit a958027ee6
12 files changed
+174 -70

No files matched your search

+11 -14
View File
@@ -17,24 +17,21 @@ The original entry starts with the line:
main(){};
This works on some 4.3BSD systems. Why? Note that #include <stdio.h>
is given on the last line. Why is this needed? Note the unusual calls
to sprintf.
This works on some systems. Why? Note that `#include <stdio.h>` is given on
the last line. Why is this needed? Note the unusual calls to sprintf.
NOTE: The program relies heavily on ASCII. Don't even think of
running it on an EBCDIC machine. If you name the file anything
other than "isaak.c", you must change the #include on line 7.
NOTE: The program relies heavily on ASCII. Don't even think of running it on
an EBCDIC machine. If you name the file anything other than "isaak.c", you must
change the `#include` on line 7.
NOTE: The use of null comments to separate macros to construct different
tokens from a single macro (e.g., "O/**/O" creates either "++" or "--"
by defining "O" to be "+" or "-") may cause some strict ANSI
C preprocessors to object.
NOTE: The use of null comments to separate macros to construct different tokens
from a single macro (e.g., `"O/**/O"` creates either `++` or `--` by defining
`O` to be `+` or `-`) may cause some strict ANSI C preprocessors to object.
NOTE: Most System V machines will not be able to execute this program
correctly due to the fact that BSD style systems have an sprintf()
that returns a char *.
NOTE: Most System V machines will not be able to execute this program correctly
due to the fact that BSD style systems have an sprintf() that returns a `char *`.
Due to the above problems, we have replaced the output of this program
Due to the above problems, we have placed the output of this program
in the file: isaak.encode. To read this file do:
uudecode < isaak.encode