Landon Curt Noll
4ee4c731f7
While not strictly necessary, replacing the two ASCII tab characters in the markdown copyright comment makes it easier to detect problematic TAB indentation within markdown files. After this commit, only 90 markdown files have leading ASCII TAB characters. And again, while not strictly necessary, we can consider running expand on those 90 markdown files to see what effect that might have on the HTML files they produce. Replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters (the default action of the `expand(1)` tool) might have an negative effect on some HTML formatting where **hack-a-round** formatting was attempted to fix broken indentation caused by problematic ASCII TAB characters. Think of this as a baseline for evaluating leading TAB characters within markdown files. TODO: Consider either using `expand(1)` to replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters AND/OR modifying the appropriate `bin` tool to convert leading ASCII TAB characters into multiples of 8 ASCII SPACE characters.
1.3 KiB
1.3 KiB
To build:
make all
Try:
./robison 80 10
./robison 40 16
The first and second parameters are optional. You might also try:
./robison 80 2 # <--- can you find the bug?
./robison 80 -246
Judges' remarks:
The following might make an interesting benchmark:
./robison 100
[Amdahl 5890-300E with System V cc: 8.40 seconds]
We suggest that you C pre-process and perhaps C-beautify this program.
All is not what it may appear to be in this program. Why does a whi1e
not take a while to execute?
Author's remarks:
This program shows that C has many unnecessary constructs, in fact
only while,--, and >= are required. (The two assignments at
the beginning could be avoided if atoi(3) was rewritten with this
new paradigm.) Note that the lack of both the controversial goto
and assignment statements makes the meaning crystal clear. The current
ANSI committee should look into this practical simplification of C.