filtoid

Caution CW: contains simulated road accident resulting in death - was considered safe for TV in the UK

https://youtu.be/mKHY69AFstE

I think OP was picturing a situation like this.

A Choose your own ~~Adventure~~ Rejection

Edit: didn't remember strikethrough formatting correctly

I'd never really thought about until now, but do Chinese (specifically mandarin speaking) 3 year olds use Ma in place of the English speaking equivalent of "why" (repeated ad nauseum until the adult being questioned snaps!)?

Ooooohhh....it's a scythe

It's either Nasal or Aural, and I'm actually not sure which would least worst

I actually disagree with that, if I saw a larger gentleman wearing this I'd feel proud of him for owning his thing with self-depracating humour, and think it was funny, the same as I do here.

It's Latin for "a person not welcome"

Thank you for sharing this. I'm going to try it out on my Italian friends :)

Yes, particularly as I get older the equipment doesn't drain fully and needs a little help.

There's a rhyme about it "no matter how much you shake and dance, the last few drops go down your pants", well I choose to wipe instead of relying on the absorbance of my pants or trousers (the original saying is American so means trousers really).

At the end of the article, which is already a litany of clownish buffoonery, it states that after destroying (effectively) the MRI machine in order to retrieve the rifle, he failed to retrieve a loaded magazine. So it was just left on the floor as they left.

Edit: autocorrect had changed it to clownfish

You are correct, I had misremembered how it works. It can evaluate build arguments, but they have to be numerical. However you can define new variables (in the pre-processor, not in code - ie, after a #) to replace those numbers, to make the intent clearer. Eg.

#define DEBUG_1 1

#define DEBUG_2 2

#if DEBUG_LEVEL >= DEBUG_1

Then pass the build arg DEBUG_LEVEL at compile time

More info here:

https://learn.microsoft.com/en-us/cpp/preprocessor/hash-if-hash-elif-hash-else-and-hash-endif-directives-c-cpp?view=msvc-170

Edit: formatting of code snippet

I'm going to take a shot at answering this, but please bear in mind that it's been a long time since I looked into the C pre-parser.

#if allows for arbitrary Boolean logic, eg #if build_env "local"

#if defined us to see if a thing has been defined already, quite often used to make sure that a header file is only imported once, redeclaration of headers is a compiler error. Eg. #if !defined(__SOME_UNIQUE_FILE_IDENTIFIER) (then define the class) then write your #endif

#ifdef wasn't always standard and was added later in the ANSI spec be a keyword, it's shorthand for the same thing as #if defined. -

This is my understanding anyway, I'm going with the principal that someone who knows more will be more likely to post a rebuttal (which I encourage).