Me after I got fired

Or just both

That exact version will end up making "true" false any time it appears on a line number that is divisible by 10.

During the compilation, "true" would be replaced by that statement and within the statement, "LINE_" would be replaced by the line number of the current line. So at runtime, you end up witb the line number modulo 10 (%10). In C, something is true if its value is not 0. So for e.g., lines 4, 17, 116, 39, it ends up being true. For line numbers that can be divided by 10, the result is zero, and thus false.

In reality the compiler would optimise that modulo operation away and pre-calculate the result during compilation.

The original version constantly behaves differently at runtime, this version would always give the same result... Unless you change any line and recompile.

The original version is also super likely to be actually true. This version would be false very often. You could reduce the likelihood by increasing the 10, but you can't make it too high or it will never be triggered.

One downside compared to the original version is that the value of "true" can be 10 different things (anything between 0 and 9), so you would get a lot more weird behaviour since "1 == true" would not always be true.

A slightly more consistent version would be

 undefined

        ((__LINE__ % 10) > 0)
  

__LINE__ returns the line of code its on, and % 10 means "remainder 10." Examples:

 undefined

    
1 % 10 == 1
...
8 % 10 == 8
9 % 10 == 9
10 % 10 == 0 <-- loops back to 0
11 % 10 == 1
12 % 10 == 2
...
19 % 10 == 9
20 % 10 == 0
21 % 10 == 1

  

In code, 0 means false and 1 (and 2, 3, 4, ...) means true.

So, if on line 10, you say:

 c

    
int dont_delete_database = true;


  

then it will expand to:

 c

    
int dont_delete_database = ( 10 % 10 );
// 10 % 10 == 0 which means false
// database dies...


  

if you add a line before it, so that the code moves to line 11, then suddenly it works:

 c

    
// THIS COMMENT PREVENTS DATABASE FROM DYING
int dont_delete_database = ( 11 % 10 );
// 11 % 10 == 1, which means true

  

A lot of these replies have high hopes for 5 year olds

__ LINE __ is a preprocessor macro. It will be replaced with the line number it is written on when the code is compiled. Macros aren't processed when debugging. So the code will be skipped during debug but appear in the compiled program, meaning the program will work fine during debug but occasionally not work after compile.

"__ LINE __ % 10" returns 0 if the line number is divisible by 10 and non-zero if not. 0 is considered false and non-zero is considered true.

#define is also macro. In this case, it will replace all instances of "true" with something that will only sometimes evaluate to true when the program is compiled.

Every tenth line, this would evaluate to False, while on lines that aren't multiples of ten, it would evaluate to True.

only when your coordinates were within a train depot in Poland?

https://www.youtube.com/watch?v=XrlrbfGZo2k

I kinda want to hear more of this story... care to share the details? i.e. what was the root cause?