sleepingkirby
Well-Known Member
- Aug 8, 2017
- 1,297
- 1,931
- 262
I'm not saying what came before it was bad. I'm saying that people use to name functions like class1_obj() class2_obj() and that's bad. Here's the line I was taught in college. (Paraphrasing because it's been 20+ years), "Giving every function its own name was okay at the start. But as programs got larger and got more complex, people started running into issues like name collision or scope issues. This is solved by namespaces and OOP."I'm not trying to disqualify anything you said or join in on this argument. OOP was popularized by c++ which lead to Java, probably the most used language out there. So we did not invent OOP because what came before was bad; it happend because Bjarne liked OOP.
But to your point... I was told/taught that the need for greater organization was what gave birth to OOP but, since you mentioned it, I don't know if I've ever looked that up for myself... *looks it up*
Here we go (
You must be registered to see the links
):Terminology invoking "objects" in the modern sense of object-oriented programming made its first appearance at theYou must be registered to see the linksgroup atYou must be registered to see the linksin the late 1950s and early 1960s. "Object" referred toYou must be registered to see the linksatoms with identified properties (attributes).You must be registered to see the linksYou must be registered to see the links
Yeah... I remember my mentor telling me about smalltalk...Influenced by the work at MIT and the Simula language, in November 1966You must be registered to see the linksbegan working on ideas that would eventually be incorporated into theYou must be registered to see the linksprogramming language. Kay used the term "object-oriented programming" in conversation as early as 1967.You must be registered to see the links
In the mid-1980sYou must be registered to see the linkswas developed byYou must be registered to see the links, who had used Smalltalk atYou must be registered to see the links.You must be registered to see the links, who had used Simula for his PhD thesis, created the object-orientedYou must be registered to see the links.You must be registered to see the linksIn 1985,You must be registered to see the linksalso produced the first design of theYou must be registered to see the links. Focused on software quality,
Okay, this is what I was referring to:You must be registered to see the linkssupport provides the ability to group procedures into files and modules for organizational purposes. Modules areYou must be registered to see the linksso identifiers in one module will not conflict with a procedure or variable sharing the same name in another file or module.
DataYou must be registered to see the linksis a design pattern in which data are visible only to semantically related functions, to prevent misuse. The success of data abstraction leads to frequent incorporation ofYou must be registered to see the linksas a design principle in object-oriented and pure functional programming. Similarly,You must be registered to see the linksprevents external code from being concerned with the internal workings of an object...It also encourages programmers to put all the code that is concerned with a certain set of data in the same class, which organizes it for easy comprehension by other programmers. Encapsulation is a technique that encouragesYou must be registered to see the links.
By the way, the most used programming language now isn't Java. Might have been true in the late 90's~early 2000's. But these days, it's javascript.
Last edited: