News for hackers. Stuff that matters.

A comment on Inheritance versus Composition. Parent comment

Re:Inheritance versus Composition by yourbandsucks on Wednesday May 08, 2019 @10:16PM (#19864802)
I mean, you can do pure functions. And those pure functions can operate on structs. And, once you're there, it's probably good hygiene to keep all the functions operating on a given struct in one file.

Congrats, you're back to 'encapsulation'! Encapsulation is actually the only important tool in that particular toolkit. We're mortals, we need coping tools to keep programs manageable.

[ Parent | on HN ]
Re:Inheritance versus Composition by TeMPOraL on Thursday May 09, 2019 @05:51AM (#19866746)
That kind of "encapsulation" is simply storing code together with the data it belongs to (good practice) and possibly namespacing it together. It's not what they mean by "encapsulation" in OO courses, though it's arguably the only benefits "encapsulation" give you.
[ Parent | on HN ]
Re:Inheritance versus Composition by erikpukinskis on Wednesday May 08, 2019 @10:39PM (#19864897)
Would you be interested in doing a podcast together about programming? I'm a radical javascript programmer (search ONNEMI-4211). You seem smart. I've never made a podcast before.
[ Parent | on HN ]
Re:Inheritance versus Composition by yourbandsucks on Wednesday May 08, 2019 @11:18PM (#19865071)
On the one hand, you've got some amazing satire here, on the other hand, I'm a little insulted that it's directed at me of all people.

Upvoted anyways :)

[ Parent | on HN ]
Re:Inheritance versus Composition by erikpukinskis on Thursday May 09, 2019 @06:54PM (#19873257)
Satire?
[ Parent | on HN ]