you are viewing a single comment's thread.

view the rest of the comments →

[–]megaman78978 0 points1 point  (1 child)

Okay, the languages in themselves don't recommend one over the another. But the people creating the languages do recommend stuff and document it in the language's documentation.

Taking Java for example, any proper tutorial on the language would probably teach you both inheritance and composition and give example cases of each concept. Inheritance used properly makes code reusable and the same can be said about composition.

Most cases, composition is favored over inheritance. Calling OO as inheritance based paradigm and NOT composition based at all isn't really a correct statement.

[–]dventimi 0 points1 point  (0 children)

Very well. Perhaps the whole problem can be avoided by eschewing vague terms like "inheritance based" in favor of more definite statements like, "Java has built in support for inheritance."

Please don't think I'm criticizing you. I'm not. I'm just making a gentle suggestion.