advanced (lemmy.world)
top 31 comments
sorted by: hot top new old
[-] lobsticle@lemmy.world 60 points 2 weeks ago

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

[-] SpaceNoodle@lemmy.world 25 points 2 weeks 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 13 points 2 weeks ago

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

[-] AceBonobo@lemmy.world 6 points 2 weeks ago

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

[-] Duralf@lemmy.world 1 points 2 weeks ago

Fair enough, I do love being contrarian

[-] AlmightySnoo@lemmy.world 6 points 2 weeks ago* (last edited 2 weeks 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 2 weeks 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 2 weeks 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 2 weeks 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 2 weeks ago

Tell this to my -Wall -Werror

[-] AlmightySnoo@lemmy.world 3 points 2 weeks 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 2 weeks ago

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

[-] Magister@lemmy.world 2 points 2 weeks 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

[-] Bishma@discuss.tchncs.de 48 points 2 weeks ago

I was going through some js code a few months ago and every function in a module had return; as its first line. And that module was imported into 4 or 5 scripts.

[-] Jupy@linux.community 22 points 2 weeks ago

You folks have clearly not met first year CS students. Screenshots code

[-] AlmightySnoo@lemmy.world 20 points 2 weeks ago

laughing in #if 0:


int main()
#if 0
        std::cout << "Look at this" << std::endl;
        std::cout << "ugly abomination." << std::endl;
[-] xmunk@sh.itjust.works 9 points 2 weeks ago

If you're in a language that supports it, please don't use if (false) use if ($disallowAllUsers = false && $whateverTheRealConditionIs)

[-] PlexSheep@feddit.de 6 points 2 weeks ago

Never seen this, what language or buildsystem is this?

[-] xmunk@sh.itjust.works 3 points 2 weeks ago* (last edited 2 weeks ago)

That specific language is PHP, but the tip is applicable in any language that supports inline assignment.

[-] TheOctonaut@mander.xyz 6 points 2 weeks ago
if (true === $wantToCauseErrorsForFun) {
[-] kogasa@programming.dev 1 points 2 weeks ago

The assignment syntax is too close to comparison, which is what is more typical in that position. I would recommend

const bool _isFeatureEnabled = false;
if (_isFeatureEnabled && ...)

if not a proper feature flag (or just remove the code).

[-] SpaceNoodle@lemmy.world -1 points 2 weeks ago

It seems much worse to use a setter in an if statement.

[-] xmunk@sh.itjust.works 0 points 2 weeks ago

Think of it as inline attribution/documentation.

[-] cupcakezealot@lemmy.blahaj.zone 8 points 2 weeks ago

bonus points if you use a different variable every file so they have to go through and change every instance if they want to make changes

[-] Bankenstein@feddit.de 5 points 2 weeks ago
[-] Asudox@lemmy.world 4 points 2 weeks ago* (last edited 2 weeks ago)

I don't see the need for an if block or renaming the function and leaving it there. It is extra unnecessary work for the compiler. Comments are probably the best way. Might also copy the current file, put the original in some folder like "old", and delete the old code inside the new copy.

[-] dmrzl@programming.dev 9 points 2 weeks ago* (last edited 2 weeks ago)

Comments are the worst as they are ignored by refactoring. That's the reason if (false) is actually really good for temporarily disabled code.

[-] jormaig@programming.dev 1 points 2 weeks ago

I never thought of that. That's quite smart!

[-] frobeniusnorm@lemmy.world 3 points 2 weeks ago

On a modern computer dead code analysis with constant folding should be nearly unnoticeable when compiling a large project

[-] FiskFisk33@startrek.website 1 points 2 weeks ago

what about relying on the persistent undo history in vim?

this post was submitted on 21 Nov 2023
411 points (96.8% liked)

Programmer Humor

2 readers
73 users here now

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


founded 4 years ago