Talk:Class-based programming
| This redirect does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||
| ||||||||
Merger proposal (2008)
[edit]Should this page be merged with "Class (computer science)"? — Preceding unsigned comment added by 70.77.102.243 (talk • contribs) 16:11, 30 January 2008 (UTC)
- Class-based programming does not seem like a popular term. So. yeah seems like a good idea to merge the content into Class (computer science). Stevebroshar (talk) 23:11, 27 July 2024 (UTC)
- I agree. Both class-based programming and object-based programming aren't popular terms and are very rarely used. Not even Barbara Liskov cites CLU as a possible class-based language if we consider "object-oriented" exists only "with inheritance," which it's a very common misunderstanding as well.
- Even if CLU were class-based, that label isn't commonly used to distinguish it of object-oriented programming, so it doesn't very important. There is a misunderstanding that OOP languages are class-based type, but in fact OOP uses both class-based and object-based approaches; that doesn't make OOP a subtype or supertype of some. QuantumNinus (talk) 18:18, 15 November 2025 (UTC)
That's not inheritance
[edit]WRT: Class-based programming ... is a style of OOP in which inheritance occurs via defining classes of objects, instead of inheritance occurring via the objects alone (compare prototype-based programming). Definitely not! Instantiation is sortof like inheritance, but inheritance is something different. For class-based, objects are created (instantiated) from classes whereas for prototype-based, an object is created based on an object. Stevebroshar (talk) 00:55, 28 July 2024 (UTC)
- There isn't inheritance in class-based programming. The definition was a misunderstanding and incorrect. I have updated it. JuUunIOr (talk) 22:32, 6 November 2025 (UTC)