• lobsticle 🦞
    link
    fedilink
    603 months ago

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

    • @SpaceNoodle
      link
      fedilink
      243 months 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
        link
        fedilink
        133 months ago

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

        • AlmightySnoo 🐢🇮🇱🇺🇦
          link
          fedilink
          6
          edit-2
          3 months 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
            link
            fedilink
            103 months 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.

            • 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 [he/him]
                link
                fedilink
                English
                33 months 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.

      • @[email protected]
        link
        fedilink
        23 months ago

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

    • @Magister
      link
      fedilink
      23 months 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