Chris said:
It should be back up now. Week end maintenance :-(
Great! It's hilarious and terrifyingly realistic at the same
time...
[The following is not meant as serious guideline]
However, you managed to not sufficiently un-restrict people's
creativity in some points:
I suggest more rules on (ab)using bit operations, e.g.
- XOR swapping for efficiency
- & and | to emulate non-shorcircuited logic operations
- using bit operations whenever you can -- they are always faster
In addition, a programmer should expand his or her horizon and
abilities by making arbitrary impromptu tests like "let's see
whether I can write this function/module without using directives
x, y, z and operators a, b, c".
switch followed by a compound statement gives room for
optimizations like restricting the scope of auxiliary variables
to this statement only, on-the-fly Duff's Device like partial
loop unrolling etc.
The obvious lack of mentioning gets() for the case of "knowing
thy input" may even be seen as malicious neglect.
Cheers ;-)
Michael