1y ago

advanced

32 comments

Very disappointing not to see an #if 0 (my personal go-to for decades) in this meme. 😞
- 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.
  
  If (false) is good because it is compiled so it doesn't get stale.
- beat me to it too, it's a meme of course but the advantage compared to comments is thay you get syntax highlighting 😁
  
  My linter always skips preprocessors not set to build, in c# at least, greys it all out unfortunately
- 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

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.

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

laughing in #if 0:

 undefined

    
#include 

int main()
{
#if 0
        std::cout &lt;&lt; "Look at this" &lt;&lt; std::endl;
#else
        std::cout &lt;&lt; "ugly abomination." &lt;&lt; std::endl;
#endif
}

If you're in a language that supports it, please don't use if (false) use if ($disallowAllUsers = false && $whateverTheRealConditionIs)
- Never seen this, what language or buildsystem is this?
  
  That specific language is PHP, but the tip is applicable in any language that supports inline assignment.
- The assignment syntax is too close to comparison, which is what is more typical in that position. I would recommend
  undefined
  
  const bool _isFeatureEnabled = false; if (_isFeatureEnabled && ...)
  if not a proper feature flag (or just remove the code).
- It seems much worse to use a setter in an if statement.
  
  Think of it as inline attribution/documentation.

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

[Ctrl-V]69jI// [Esc]
- gc69j

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.
- Comments are the worst as they are ignored by refactoring. That's the reason if (false) is actually really good for temporarily disabled code.
  
  I never thought of that. That's quite smart!
- On a modern computer dead code analysis with constant folding should be nearly unnoticeable when compiling a large project

what about relying on the persistent undo history in vim?

In Python you put it in a multiline string, since it has those but not multiline comments.

32 comments