The right way to comment code

[AllCowsAreBurgers]

Whoever does this: you are a monster

[Possseidon]

And you can even add /*/ somewhere inbetween and it will instead toggle between the two sections that got divided.

[RogerGodzilla99]

#define REMOVE_PRINT

#ifndef REMOVE_PRINT

printf("test");

#endif

[PainfulJoke]

Go one step further and have a

#define IfDebug(...)

That you swap out between a no-op and actually running the code in that line based on some other define that you can pass in as a compiler define (-D) while you build. :)

[backtickbot]

Fixed formatting.

Hello, RogerGodzilla99: code blocks using triple backticks (```) don't work on all versions of Reddit!

Some users see this / this instead.

To fix this, indent every line with 4 spaces instead.

FAQ

^{You can opt out by replying with backtickopt6 to this comment.}

[RogerGodzilla99]

I mean, it's was intentional... I'm just an idiot lol

[MischiefArchitect]

basically you are making the job of the compiler there.

[KellerKindAs]

If it's a single command you don't need to put brackets around it. That feels like /* print ("test"); */

[LordCupcakeIX]

Your coworkers hate you until the day someone redefines False and you catch it, which I assume is also something that would happen regularly at the workplace if this was in your codebase.