Re:Inheritance versus Composition
by marcosdumay on Thursday May 09, 2019 @01:10PM
(#19870082)
Yeah, and Python has some standard nomenclature for marking a property as protected and a little bit of behavior for helping mark it as private. You do not need encapsulation for that.
Re:Inheritance versus Composition
by scarface74 on Thursday May 09, 2019 @01:33PM
(#19870278)
And there is nothing about the Pythom runtime stopping someone from using it anyway.
With a statically typed language, you really have to go out of your way to do it like using reflection and if your code breaks on an update you get what you deserve.
Re:Inheritance versus Composition
by kevin_thibedeau on Thursday May 09, 2019 @11:31AM
(#19869154)
YAGNI rules the day.
Re:Inheritance versus Composition
by scarface74 on Thursday May 09, 2019 @12:49PM
(#19869865)
You’ve never had to refactor code that was used as a library by other developers?
Do you realize how many hacks is built into Windows just because developers were using undocumented features?
It’s about intention. If I mark a property or method as private, it means that I can get rid of it, rename it or change the expected behavior without considering it a breaking chance.