https://www.youtube.com/watch?v=_ZwiMlyeQNU&t=15s
In short, kids with little to no programming experience teach other disorientated desperate kids with few career opportunities in a country with a primitive economy.
I repeat all statements in my code for exactly this reason. Sometimes I even compile the same code twice. You can never be too careful.
That guy has a great career ahead in comedy!
In my case I had some cleanup code to run at the end of the function in an error case, so I used "goto fail;" instead of "return;". And then just to be sure it always worked, I put in the "goto fail;" twice!
Technically incorrect, but how many of the top 20 languages (https://www.tiobe.com/tiobe-index/) have c style macros? I don't think many of them have a pre-processor at all.
Some of those languages, like Python and C#, have advanced features which eliminate much of the need for macros. Others, like JavaScript and SQL, would be much improved by assembly-language or Lisp style macros.
The claim that macros do not exist in other languages is incorrect. Every sensible assembly language compiler has macros to help the programmer with boilerplate.
The claim that multiline macros are a problem is correct. Suggesting that a workaround is to use a naming convention for such macros is crazy-talk. There is a time-honored pattern you use to fix this in the macro itself: wrap the macro with "do { <macro content> } while (0)".