this post was submitted on 02 Sep 2024
888 points (99.2% liked)

Programmer Humor

32483 readers
500 users here now

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

Rules:

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
cat_programmer@lemmy.ml
888
The C++ learning process (aussie.zone)
submitted 2 months ago by unionagainstdhmo@aussie.zone to c/programmerhumor@lemmy.ml
130 comments fedilink hide all child comments
 

Incase it doesn't show up:

you are viewing a single comment's thread
view the rest of the comments
[–] jaybone@lemmy.world 3 points 2 months ago (1 children)

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.

[–] magic_lobster_party@fedia.io 1 points 2 months ago (1 children)

If the lists have shared components then that can be solved with composition. It’s semantically the same as using abstract classes, but with the difference that this code dependency doesn’t need to be exposed to the outside. This makes the dependency more loosely coupled.

[–] jaybone@lemmy.world 1 points 2 months ago (1 children)

In my example, how is the code dependency exposed to the outside? The caller only knows about the List interface in my example.

[–] magic_lobster_party@fedia.io 0 points 2 months ago (1 children)

In your example, the declaration of ArrayList look like:

public class ArrayList extends AbstractList implements List {
}

The dependence on AbstractList is public. Any public method in AbstractList is also accessible from the outside. It opens up for tricky dependencies that can be difficult to unravel.

Compare it with my solution:

public class ArrayList implements List {
    private AbstractList = new AbstractList();
}

Nothing about the internals of ArrayList is exposed. You’re free to change the internals however you want. There’s no chance any outside code will depend on this implementation detail.

[–] SpaceNoodle@lemmy.world 1 points 2 months ago

That's not C++, which has more control over such scope.