this post was submitted on 13 Apr 2024
730 points (95.9% liked)

linuxmemes

20880 readers
5 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
730
Supreme leader mad (sh.itjust.works)
submitted 7 months ago by [email protected] to c/[email protected]
101 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 7 months ago

Well yes, I get the differerence between an interface and a class, and what I write is typically a class, which contains properties and functionality that may or may not be overridden in derived classes.

For example, calling a parent class implementation can be useful when I have a derived model that needs to validate its input in some specific way, but otherwise does the same as the base class.

What I don't understand is why this makes OOP bad?