412
advanced (lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
[-] lobsticle@lemmy.world 61 points 1 year ago

Very disappointing not to see an #if 0 (my personal go-to for decades) in this meme. ๐Ÿ˜ž

[-] SpaceNoodle@lemmy.world 25 points 1 year ago

Damn, you beat me to it.

It's common enough that it's supported like a comment by numerous syntax highlighting schemes, and has the added benefits of guaranteeing that the code won't be compiled as well as encapsulating any pre-existing block comments. Conversely, if (false) is total garbage.

[-] Duralf@lemmy.world 14 points 1 year ago

If (false) is good because it is compiled so it doesn't get stale.

[-] AceBonobo@lemmy.world 6 points 1 year ago

"you're not wrong, you're just an asshole"

[-] Duralf@lemmy.world 1 points 1 year ago

Fair enough, I do love being contrarian

[-] AlmightySnoo@lemmy.world 6 points 1 year ago* (last edited 1 year ago)

A simple if (false) will get optimized out by any modern C or C++ compiler with optimizations on, but the problem is that the compiler will still parse and spend time on what's inside the if-block and it has to be legal code, whereas with the #if 0 trick the whole thing gets yeeted away by the preprocessor before even the compiler gets to look at it regardless of whether that block contains errors or not, it's literally just a string manipulation.

[-] Duralf@lemmy.world 10 points 1 year ago

I think you missed the whole point of my comment ๐Ÿ˜‚. Regardless, the time spent compiling a small snippet of code is completely negligible. In the end, both #if 0 and if (false) have their complimentary uses.

[-] AlmightySnoo@lemmy.world -1 points 1 year ago

Yeah, but I still think if (false) is silly because it adds an artificial constraint which is to make sure the disabled parts always compile even when you're not using them. The equivalent of that would be having to check that all the revisions of a single source file compile against your current codebase.

[-] fushuan@lemm.ee 3 points 1 year ago

If(false) works in interpreted languages, the other one doesn't. It's stupid either way, that's what version control is for, but if we are doing the stupidness anyway, you can't use preprocessor flags in many languages because shit doesn't get compiled.

[-] pelya@lemmy.world 2 points 1 year ago

Tell this to my -Wall -Werror

[-] AlmightySnoo@lemmy.world 3 points 1 year ago

beat me to it too, it's a meme of course but the advantage compared to comments is thay you get syntax highlighting ๐Ÿ˜

[-] KeenFlame@feddit.nu 2 points 1 year ago

My linter always skips preprocessors not set to build, in c# at least, greys it all out unfortunately

[-] Magister@lemmy.world 2 points 1 year ago

this is what I'm doing too, so at least it's not compiled and better than a /* */ as you can keep all the code intact in your #if 0

this post was submitted on 21 Nov 2023
412 points (96.6% liked)

Programmer Humor

32572 readers
309 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS