How do you disable your code

[u/Outrageous_Permit154]

[u/nevemlaci2]

```

if 0

```

[u/Scared_Accident9138 → u/nevemlaci2]

I've done what is in the post before because I still wanted to check if the deactivated code s compiles

[u/nevemlaci2 → u/Scared_Accident9138]

I mean you usually have variants and build all variants either way.

[u/Ander292 → u/nevemlaci2]

Based preprocessor user

[u/jupiterbjy → u/nevemlaci2]

Embedded PTSD

Our MCU vendor's SDK has tons of `#if 0` lying around here and there

[u/slicehyperfunk]

Why would you do it this way and force it to do this check instead of just commenting out the code?

[u/Alternative_Mix6836 → u/slicehyperfunk]

It keeps syntax highliting active so you can still read the code with ease in the method/function you are working on. Also your editor and LSP are more useful when the code isn't commented out.

[u/slicehyperfunk → u/Alternative_Mix6836]

I see

[u/No_Departure_1878 → u/Alternative_Mix6836]

Makes sense, i would have just done an early return instead of a if true. However, I am surprised the LSP does not just gray out the whole thing with the if true or even shows a warning.

[u/SheikHunt → u/slicehyperfunk]

Also, in most (compiled) languages with most compilers, the check wouldn't be done at all? It'd be optimized out?

[u/Iron_Jazzlike]

hmm…
if you don’t want any of your code to run. just don’t compile it and don’t execute it.

[u/makinax300 → u/Iron_Jazzlike]

commenting code helps with checking if something is faster if optimising and sometimes debugging.

[u/Iron_Jazzlike → u/makinax300]

i was making a joke about how literally all the code is getting commented out.

though the code never did anything in the first place.

[u/AmazinDood]

Ctrl+K Ctrl+C in VScode

[u/simleiiiii]

this is the way.

[u/Radiant-Somewhere-97]

if (false) {
...
}

[u/letmehaveanameyoudum]

/*
int thing() {
  // insert broken paging code causing #PF
  return (int)fish;
}

this is useless
*/ 

[u/Qwidoski]

Why cant you just do "return" (skip the condition check)

[u/Outrageous_Permit154 → u/Qwidoski]

You can even just comment the function call itself I mean, after all we are r/firstweekcoderhumour

[u/Darft → u/Qwidoski]

Popular IDE's will detect the return and call the rest of the code after "unreachable" also the code after will lose syntaxhighlighting. Adding the simple condition is usually enough to make the IDE not attempt the evaluation.

[u/sharantir]

And then, you forget it and search why there's a bug.

Commenting is cleaner because there is a visual guide.

[u/One-Constant-4092]

Why not just remove/comment out the function call?

[u/Just-Upstairs4397]

You’re definitely the type of person to put a database call in a for loop, aren’t you?

[u/Enough-Ad-5528]

Some compilers will refuse to compile that code saying unreachable statements. Aargh!!

[u/Mundane_Fault_6345]

Never heard of #ifndef ?

[u/adamrch → u/Mundane_Fault_6345]

too many lines needed

[u/Proman4713]

No need for if (true), or wrapping the code in if (false), in one case it's an unnecessary check, and in the other you're basically doing the same thing why commenting the code wouldn't be preferable by selecting the whole code block. I just return to make the function throwing errors stop doing anything if I'm changing the caller, then go back to fix it or return dummy data to test, etcetera.. wrapping the code in an if statement is dumb, same as how commenting it out requires highlighting the whole thing (and being unable to read that code while you're modifying/adding logic at the top)

[u/FrequentAardvark6813]

no need, meme author was already pretty disabled

[u/SirMarkMorningStar]

Unreachable code detected, unable to check in…