Talk:Object (computer science)

From Wikipedia, the free encyclopedia

 This article is within the scope of WikiProject Computer science, which aims to create a comprehensive computer science reference for Wikipedia. Visit the project page for more information and to join in on related discussions.
Start rated as Start-Class on the assessment scale
High rated as High-importance on the assessment scale

This should be moved back to Object (object-oriented programming) for two reasons.

  1. It would be consistent with other topics uner OOP
  2. There are other examples of objects in computer science which do not strictly conform to the definition given in this article. e.g. the Old Object model of Visual Basic.

Sorry but this really doesn't make sense at all. -- Taku 07:03, Oct 13, 2003 (UTC)

personaly, i think it should all stay here, and a redirect from Object (object-oriented programming) to here. tooto 17:21, 6 Aug 2004 (UTC)

Contents

[edit] Removed some material to avoid mis-attribution

When editing said page, Taku moved some items to Talk: and then signed his action. Unfortunately, unless you follow the edit history, it then becomes difficult to separate what he said from what he is signing.

Therefore, I deleted the material and left only the fact that he moved it from said page.

[edit] Is the sample source code mis-leading?

Isn't example in this hypothetical language a little bit mis-leading? Shouldn't Fido and Princess be declared of type Dog? Why not use something standard such as Java or C++ in the first place? --Esad 17:15, 8 Feb 2005 (UTC)

[edit] Class-based only

This article on talks about class-based OOP. Wouter Lievens 12:30, 3 Apr 2005 (UTC)

I know. That's a problem. -- Taku 18:45, Apr 3, 2005 (UTC)

[edit] Circular links

Under the heading "Objects in Object-Oriented Programming", instantiating points a disambiguate page which leads you to Instance (programming) which is a redirect to Object (computer science). In the next para, Instance points to Instance (programming) which, as before, redirects you back to Object (computer science).

I know you OO types love being self-referential, but it doesn't work so well in a Wiki... Shermozle 15:09, 15 December 2005 (UTC)

Thanks for pointing this out. It's still a problem... —Pengo 11:28, 30 May 2006 (UTC)
Now it appears to point to instantiation, which is a disambiguation page. I think I will remove this link altogether. --Spoon! 07:07, 4 September 2006 (UTC)

[edit] Add some examples

Please add some examples to this article. --Gary King 02:25, 26 January 2006 (UTC)

[edit] Best Quote Ever

"The God object is an example of an anti-pattern." I love it. Out there. I was trying to research programming languages and ended up feeling like I was looking into philosophy and theology. Anyway, I think that sentence would do well to include a brief decription of what is meant by an anti-pattern. You can click through to the link, but I think that the references in the article should be a bit more contained. It's a zinger of a sentence, but it refers to a very specific piece of knowledge that the article shouldn't assume the average reader has. Some minor explanation here would go a long way to make it a little bit less of a 'WTF?'-sounding statement. It almost comes across as a bit of sensationalism. Almost.

It is, however, a fascinating article. Kudos to those of you who put this thing together.

[edit] A candidate for deletion?

"For example, a diagram of a computer monitor is a class (let's call it monitor_class). The actual computer monitor you are looking into is an instance of that class, hence an object"

Eh? Which is the class? Is it the diagram or the computer monitor? If you instantiate an object of class "diagram" you get an instance of "diagram", not an instance of a "computer monitor". Perhaps it's trying to make an analagy between a diagram and a class definition, but if it is, then it's a poor one, poorly stated.

There are lots of other errors in this article as well. But are they worth fixing, is there anything here not already said in the object-oriented programming article?

Any reason why this article shouldn't be nominated for deletion? --Malleus Fatuarum 03:05, 12 August 2007 (UTC)

There is no reason why this article should be nominated for deletion, if you find errors then tag them with an appropriate template or fix it --Zven (talk) 02:49, 16 April 2008 (UTC)
While possibly unclear the sentence quoted is not wrong, or at least not wrong for the reasons you imply. While it is true that if you instantiate an object of class "diagram" you get an instance of "diagram". However an instance of one class might well be a class, eg. instances of the class of classes. This is a useful concept in metaprograming. In the case of the sentence quoted the problem is that it is hard to see the diagram for monitors as being the class of monitors. However it's easy to see the diagram as a representation of the class of monitors. A better wording might be For example, a diagram of a computer monitor specifies a class. The actual computer monitor you are looking into is an instance of that class, hence an object. Taemyr (talk) 09:20, 16 April 2008 (UTC)