Programmer Humor

32568 readers

748 users here now

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

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

196

OOP theory vs practice (lemmy.ml)

submitted 1 week ago by yogthos@lemmy.ml to c/programmerhumor@lemmy.ml

50 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] arrakark@10291998.xyz 10 points 1 week ago* (last edited 1 week ago) (2 children)

I straight up never got a nice answer from StackOverflow on this. Say you have 5 classes, each requiring access to the data members/functions of the others. What's a nice way to solve this problem? I've thought of only two ~~nice~~ shit methods:

Pass pointers/shared-pointers etc to each class, but not through the constructor but a setter function
Pass lambdas or std::function everywhere. Yuck! Still doesn't put each object in a valid state in the constructor.

[–] yogthos@lemmy.ml 21 points 1 week ago

The. real question is whether this problem needs to be modelled using classes in the first place. The alternative is to just have a set of composable functions that take a piece of data and return a modified version that can be passed to a different function.

[–] Kayana@ttrpg.network 17 points 1 week ago

Well, what problems are you trying to solve by having the classes all access each other's data members? Why is that necessary?