Talk:Object-oriented programming

I would like to rename this to object theory. I understand object-oriented programming is the most common term and nearly no one uses a word like object theory instead of it. But the trouble with the current title is OOP is a POV'd term. The situation is similar to that in socialism or communism. The majority of people claim class, inheritance and encapslation are foundamental aspects of OOP but some argue inheritance is not always necessary, for instance. It doesn't matter who is right. The fact is there are disputes regarding the definition of object-oriented programming. So it would be troublesome with the current name as some claim inheritance is an aspect of class-based OOP then the article sholdn't cover, while some say inheritance is a foundamental of OOP and there is no reason that the article doesn't cover it. I don't think such debate would be settled. The benefit of the title object theory is it is more abstract term. It can discuss languages before object-oriented programming. Ada8 something supports objects but is usually considered not OOP. Then where we should discuss such? A separate article? The title object theory implies it is about programming aspect regarding objects. It is a broader term that can contain class-based OOP, object-based programming and so on. Subprogram is an good example. People hardly uses a term subprogram over subroutines or functions. But in encyclopedia, use of such an abstract term is preferable because if the article named function, it implies a subprogram should be a function like in math, which is not the case. If named subroutine, it tends to emphasizes a behavior as side-effect and it makes hard to talk about function in functional languages. OOP is a similar case.

And as usual, if I don't see an object, I will go ahead. -- Taku 13:44 23 May 2003 (UTC)

If you want a separate article called object theory that explains differnet methods of using objects in programming languages then fine. But the aspects of the OO paradigm discussed in this article (abstraction, encapsulation, polymorphism and inheritance) is a vast subject that deserves a least a whole page devoted to it. What you have us call it? OOP is the universally understood term used for these concepts. Mintguy 14:01 23 May 2003 (UTC)

Please don't use the current content as an excuse. I want to rename first because otherwise, people will claim it is not OOP. Certainly we want to discuss what is OOP? But the more important is, history of OOP, point of views, variants, and so on. They are certainly beyond an article named object-oriented programming. Again, oftentimes, broader term serves well in encyclopedia. I showed an example above. -- Taku 15:11 23 May 2003 (UTC)

I happen to disagree with your choice of the word subprogram, in all my 25 years experience of being a programmer I can't recall anyone ever using the term subprogram for subroutine, function or procedure or method. However those four words that that you've grouped under subprogram do have different meanings to different people, usually depending on what language you are talking about. i.e. C programmers talk about functions when they mean procedures. I personally think subroutine is a better word because it is one that is in common usage and I beleive it has a longer history than the other words. But that is another issue.

Why don't we try to resolve this issue sensibly. Why don't you start writng an article about object theory and we'll see needs to be merged in from OOP? Mintguy 15:21 23 May 2003 (UTC)

About subprogram. That is exactly my point. There are a lot of concepts related to subroutine, function, procedure and methods. But we don't want to have a separate article for each one. What I am trying to do here is the same thing. Because for programmers, the difference is a huge matter, but for general audience, they want to know more about what is happening in cs. We don't want to teach them OOP should be bah bah bah. That is a difference seen in articles of wikipedia and textbooks. Because most of textbooks or websites have a POV such as OOP should be. Yeah, I can start certainly I can start an article called object theory but the trouble is we need to make sure history is combined. What about renaming this first, add more about object-based OOP and difference between class-based and object-based and then decide what name should be given or without renaming, start adding such point. This is just a chiken and egg problem. I don't care which one is first. -- Taku 16:17 23 May 2003 (UTC)

But why choose a word that no-one uses. That makes no sense whatsoever. I wouldn't expect to find an article about fishing under fish hunting. To the best of my knowledge, few people if any use the word subprogram to mean a subroutine or procedure. Subroutine is a word that assembler programmers generally use and it makes no assumption about whether there is a return value of side effect, or whether it is a member of a class or not. It just means a group of instructions that you jump to to perform a task and then jump back from continuing execution where you left off.

I am against the idea of moving this page, because by adding stuff about other systems with objects or if you like widgets that do not embody OO principles you are diluting it and moving away from OOP. Mintguy 16:30 23 May 2003 (UTC)

See this is why I need to rename first. Anyway, we always make a redirect so of course, you can find out the article, object theory. If I don't mean to stick only to that term, but other possibilities are:

• object theory
• object-orientation
• object-oriented
• object-oriented paradigm

I just want to make the title more abstract, so that the article can contain parts beyond your strict definition of object-oriented programming. -- Taku 16:45 23 May 2003 (UTC)