Incase it doesn’t show up:

    • magic_lobster_party@fedia.io
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      Ask Bjarne to add interfaces enough many times until he gives in.

      On a more serious note, I’m not exactly sure what the best C++ practice is. I guess you just have to live with abstract classes if you really want interfaces.

        • magic_lobster_party@fedia.io
          link
          fedilink
          arrow-up
          2
          ·
          2 months ago

          The only problem is to ensure the entire team agrees to only use it like an interface and nothing else. But I guess that’s the only proper way to do it in C++, for now.

          • SpaceNoodle@lemmy.world
            link
            fedilink
            arrow-up
            3
            ·
            2 months ago

            That’s not really the job of the language, though. If they can’t read the design docs and source annotations, they don’t really have any business touching anything.

          • affiliate@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            2 months ago

            this seems like the only proper way to do anything in C++. it’s a language where there’s 5 ways to do 1 thing and 1 way to do 5 things.

    • pelya@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      I know at least three ways, one of them involves variadic macros.

      You don’t even need to look that far, take any sufficiently aged library, like OpenGL.

        • pelya@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          2 months ago

          Yet I still had an urge to explain an obvious thing. Because it’s C++, so everyhing goes. There are even tools to auto-generate C++ interfaces, because of course someone decided that C++ is inadequate and must be improved using some kind of poorly-documented ad-hoc extension language on top of C++.