> IF THEN OTHERWISE
Which avoids overloading OR and maintains better grammar.
But I suspect shorter words were preferable when space was a premium everywhere not least on the display itself.
#include <stdio.h>
#define PREACH printf
#define SHOULD_GOD_WILL if
#define EACH_AND_EVERY_CREATURE_UNDER_GODS_LIGHT for
#define OTHERWISE else
#define RETRIBUTE return
#define ALONG_WITH &&
#define THUS }
#define LET {
int main() LET
EACH_AND_EVERY_CREATURE_UNDER_GODS_LIGHT (int i = 0; i < 100; i++) LET
SHOULD_GOD_WILL (i % 5 == 0 ALONG_WITH i % 3 == 0) LET
PREACH("Fizzbuzz!\n");
THUS OTHERWISE SHOULD_GOD_WILL (i % 5 == 0) LET
PREACH("Buzz!\n");
THUS OTHERWISE SHOULD_GOD_WILL (i % 3 == 0) LET
PREACH("Fizz!\n");
THUS OTHERWISE PREACH("%d\n", i);
THUS
RETRIBUTE 0;
THUS"Utilize" first arose in 1807 if Merriam-Webster is to be believed, well past the period you're quoting; and "dost" should agree with the number of its noun "senses". ("dost" is second-person, but you need something third-person.) In this context I also don't really like the continuous present of "are you utilizing", but I can't put words to why. I believe "hast thou taken leave of thy senses" is actually recorded to be idiomatic.
By the way, ChatGPT suggests (where I've fixed its analogous error in the word "doth"):
> Pray tell, wherefore dost thou employ the term 'contrariwise'?
greater x y
| x > y = x
| otherwise = y
In Haskell's case, this is a conditional syntax that's alternative to if-then-else, so `else` was already taken. `otherwise` is just a conventional constant for `True` that's chosen for readability. if otherwise then not IF (condition) THEN (do-this) ELSE (do-that).
I think 'or' would not go with alternative commands, but with an alternative condition: IF (condition) THEN (do-this) OR (other-condition) THEN (do-that).
If you don't want to use 'else' then 'otherwise' would sound idiomatic, too.
> One minor quibble was Strachey’s objection to the grammar of “IF … THEN … ELSE” statements. “I cannot allow my name to be associated with a definite recommendation to use ignorantly incorrect English,” was his view, as Hartley later wrote for Annals of the History of Computing. Strachey preferred “OR,” which conflicted with the way “OR” was used in nearly every other programming language in existence. Nonetheless, his preferences carried the day, and the CPL reference manual included “OR” in the place where users would have expected “ELSE.”
That seems like a pretty stupid thing to do--perhaps not at the time by the 'do'ers.