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.
To build:
make all
To use:
./august
Try:
./try.sh
If you have the primes(6) tool (sometimes part of
BSD Games) you can see
what of the output in the first N (say 15 or 25) lines are primes:
./primes.sh # 15
./primes.sh 25
Note that try.sh will run this script anyway, telling you where to get
primes(6) if you don't have it installed, but it will only run with the
default value of 15, rather than trying several different values.
Judges' remarks:
An interesting use of a recursive call to main(). Compile and execute
without args. What is the initial value of b? Does it alter the
action of the program?
If you let it, the program will continue to print a numerical sequence (can you guess in what base it is printed by looking at the code?) until you run out of memory or until they sell your computer, whichever comes first.
If you use the primes.sh script can you figure out if there's anything funny going on with the output?
Author's remarks:
No remarks were provided by the author.