Landon Curt Noll
bd63d57cb5
For browsers that have JavaScript disabled, topbar puts up a link that reads "Please Enable JavaScript" instead of the so-called "hamburger menu" icon. Fixed a number of internal links that were broken when by commit `e7d69bc23270e8ad73d391d15d4c996ffbd33cc3 and perhaps a few other earlier commits. Ran `make www` to perform the above.
To build:
make all
There is an alternate version, the original, that can't be compiled in modern systems but can be if you have an old enough compiler. See Alternate code below.
To use:
./isaak
Alternate code:
The original version of this code is in isaak.alt.c. The original entry starts with the line:
main(){};
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(3).
This version also relied on being able to define #define to something else and
using that macro for #define.
This version will not likely work on modern systems if you can even get it to compile.
Alternate build:
make alt
Use isaak.alt as you would isaak above.
Judges' remarks:
The program relies heavily on ASCII. Don't even think of running it on an EBCDIC machine.
Historical notes about the original entry:
NOTE: If you named the file anything other than isaak.c, you had to
change the #include on line 6. This limitation has been fixed by using the
__FILE__ macro.
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 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 above problems, we placed the output of this program in the
file: isaak.encode. To read this file do.
uudecode < isaak.encode
cat isaak.output
Since this was fixed, this file is not strictly necessary. See the isaak.alt.c for the original source.
FYI: We are likely to be more strict about portability in the future.
Author's remarks:
No remarks were provided by the author.