make
./schneiderwent
./schneiderwent schneiderwent.data
./schneiderwent
What’s the difference?
If you have a long while to spare (and you’re bored enough that you could watch paint dry :-) ) you might also try:
./try.sh
Alternatively, you can check on it later on, to see all the entry does. Or if you wish to make it run faster, you can override how long it sleeps per iterations and how many iterations it runs. For instance to make it sleep only 30 seconds and run only twice:
SLEEP=30 ITERATIONS=2 ./try.sh
Very nice play by the rules and portable text obfuscation. This far surpasses old tricks like adding or subtracting 1 from every character in a C string.
Translating the messages into your language of preference while keeping the program portable between different encodings (Chinese, Japanese, Russian - anyone?) may be an entertaining task.
This entry displays the current time to the console, for example:
it’s just after ten ’til 6 in the evening
FWIW, none of the compilers with which this entry was tested issued any warnings or errors in compiling the source for this entry. No doubt lint will complain about the goto statements.
The schneiderwent.data file consists of the values used by multiple table lookups. This is simply good program design, separating these values from the source code allows changing the behavior of the application without recompiling.
Having learned COBOL at an early age, the pthread
s of my thought
processes tend to be translated into code in a verbose manner. Some
of the #define
s in this entry’s code are to mitigate this personal
deficiency.
Obfuscation in this entry consists of:
printf(3)
ing console messages stored as
EBCDIC character values - this is not
an attempt at encryption, but rather at cross platform compatibility.?:
operator.'J'
by 2
- the ASCII value of the
character is even, the EBCDIC value is odd.printf(3)
ed are determined via multiple table lookups and
bit-masked values.printf(3)
ed.setjmp(3)
/longjmp(3)
combination.