Content deleted Content added
TakuyaMurata (talk | contribs) No edit summary |
Stop arguing and make the article more informative. |
||
Line 93:
Besides, some people with good education and good professional experience understand nothing about OOP, though I don't know if you are the case or not. Please show us evidence of your POV not who you are. I hope you can be accustomed to the wikistyle. -- [[User:TakuyaMurata|Taku]] 18:00, Oct 21, 2003 (UTC)
----
This argument is obnoxious. Worse, there is a distinct shortage of evidence for and against different approaches. Who you are and what you know is irrelevant to whether the information is generally correct. If an issue is debatable, leave it in talk or put it on your user page and link your user page here.
I suggest that it makes no sense to call OOP a "style" of programming. If something is part of a language, it's use can hardly be a style, on par with indenting and variable naming conventions. Paradigm is an abused word, but it is much more suitable to describe a feature of a language which is built in and common to a whole group of different languages with different but related approaches.
I would request that anyone of sufficient knowledge consider expanding on the distinction between OOP and standard procedural languages, especially since many OOP languages, notably the two most popular (Java and C++) are still procedural. Many discussions of OOP seem to suggest that objects have a sort of independent existence, as if they were autonomous entities like processes. The idea, for example, that they "communicate", while nice in abstraction, is really not correct, at least not in any way especially different from how functions talk to one another. Objects are not agents, after all, they are special data structures. [[User:Brent Gulanowski|Brent Gulanowski]] 20:05, 24 Oct 2003 (UTC)
| |||