Uhhh...

Brisingr Aerowing

C/mainarray.c at master · dequbed/C · GitHub[^] I... uh... :wtf:

What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???

Jon McKee

The [multilayered switch cake](https://github.com/dequbed/C/tree/master/multilayeredswitchcake) example still has me scratching my head :doh:

MarkTJohnson

That was a thing of beauty. Duff's device to the next level. Duff's device - Wikipedia[^]

I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.

Gary Wheeler

Pardon me for being a tad dense, but... is that somehow a hand-assembled main() function, encoded in oh-so-useful decimal?

Software Zen: delete this;

Brisingr Aerowing

Pretty much.

What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???

Gary Wheeler

To coin a phrase: "Kill it before it runs." Even if something like that were technically necessary (I could see it in embedded code), an array of completely undocumented random decimal integers is beyond ridiculous. Even if the compiler doesn't support the asm keyword and inline assembly, you could still list the array contents as hexadecimal values with the corresponding assembly code in adjacent comments.

Software Zen: delete this;

Greg Utas

Also ridiculous are names that activate horizontal scroll bars. But I digress. :laugh:

Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.

Gary Wheeler

Ah, but there's a reason for the ridiculously long name. The name I listed is the longest for a group of enum values which are individual bits in a 32 bit mask. Each bit identifies a message that should be displayed to the operator. The equipment can identify a single message or several to be displayed at once. The messages don't lend themselves to any kind of consistent, concise naming scheme. As we know, the following two problems are fundamentally difficult in computing:

Cache invalidation
Creating appropriate identifiers
Off-by-1 errors

The simplest and most logically consistent naming for each bit was therefore the text for that bit, with minor transformations to convert the text into a valid C++ identifier. Space characters and all punctuation became underscores, and Bob's your uncle. Just to add to your excitement over this challenging and seemingly intransigent problem, there is ongoing grumbling from the equipment group over the text I actually display based upon each bit. They expect the exact text in their specification to be displayed. You see, I have this effete and unwanted fondness for grammatical English, which their text... isn't. We won't even mention (yes we will) the fact that our UI is also translated to French, Italian, German, Spanish, Japanese, Chinese Simplified, Korean, Polish, and Russian. Some folks just kind of expect us to speak their language.

Software Zen: delete this;