Incase it doesn’t show up:

  • magic_lobster_party@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    28 days ago

    In 99% of the cases, inheritance can easily be replaced with composition and/or interfaces. Abstract classes tend to cause hard dependencies that are tough to work with.

    I’m not sure why you would use abstract classes without data. Just use interfaces.

      • magic_lobster_party@fedia.io
        link
        fedilink
        arrow-up
        0
        ·
        28 days 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.

    • jaybone@lemmy.world
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      28 days ago

      Say List is an interface.

      You have implementations like ArrayList and LinkedList.

      Many of those method implementations will differ. But some will be identical. The identical ones go in the abstract base class, so you can share method implementation inheritance without duplicating code.

      That’s why.