Why do you say Java has the most powerful OOP system?

Why do you say Java has the most powerful OOP system?

Many languages derived from Java may have as good systems (C# for example).

But then again, not a place for debating languages.

Ashbad, I hope someone can use your help (who knows me ).

Quote from: yunhua98 on March 11, 2011, 02:40:49 pm

Quote from: merthsoft on March 11, 2011, 02:29:30 pm

Why do you say Java has the most powerful OOP system?

he says its just his opinion.  I may have misunderstood you, but Omnimaga's not a place for debating which language is the best.    Unless the topic is a poll to find out which is the community favorite. 

I know he said it was his opinion, that's why I said "why do you say" not "why is". I'm simply asking him to elaborate on his opinion about a language that is directly related to the topic. He wants us to learn OOP, I want to learn what about Java OOP he thinks makes it the best. I'm not debating him, I'm asking him a question.

Nicely said, I hope Ashbad answers it.

I personally like python because it uses indentation instead of semicolons and braces. I find it easier to read.

This is a great thread. I always thought it would be nice too have someplavce to ask questions about features of OOP languages

I think there are some things you can do without OOP, but there are many things you need OOP for. At least in my opinion it would be much easier to use OOP then another kind of language.

I thought C/C++/C# were all OOP languages
<offtopic>has anyone heard of the languages D or GO?</offtopic>

I personally like python because it uses indentation instead of semicolons and braces. I find it easier to read.

Some of my opinions (and explanations) of OOP languages:

Python: I like Python because it's really, really intuitive. Like if you want to check if ELEMENT in LIST, that's exactly it -- if ELEMENT in LIST is valid syntax. It also supports dynamic typing, meaning you can represent a single variable in many different forms, which makes things really easy because you don't have to convert back and forth.

Java This is pretty much the OOP language, meaning it's the most strictly based on the concept of OOP. The entire structure of the language is based on OOPL as a foundation; everything you do will be tied in some way to the ideas of objects and classes. That makes it great for real-life applications, but if you want something simple that doesn't really need objects, Java's strict syntax requirements can be a minor PITA.

C++: C++ is great because it's actually compiled, straight to pure executable assembly (unlike Java, which compiles to bytecode that still needs to be interpreted).

I've never used C#, so can't give any tips here.

EDIT: I realize that my sudden little OOP tutorial might have blown you guys away just a bit, seeing as no one has posted to this forum since I posted. I rewrote it a little bit.

Oh, an OOP thread! My base is in C#, which is an incredibly OOP language. I would be happy to answer any questions about OOP that you guys might have. In the meantime, I can tell you guys what the basic idea of OOP is:

In low level programming, everything is managed by the programmer. All of the objects in the game, and all of their properties, are handled directly by the programmer. For example, to define a spaceship with an X, Y, and rotation in TI-BASIC, and then move it 10 pixels forward, you would do something like:
0->X:0->Y:0->R
X+sin(R)*10->X:Y+cos(R)*10->Y

However, in OOP, all of the objects in a program are encapsulated in classes. A class is basically an object's definition, which contains all of the properties of an object. For example, in C#, you would say
class Ship
{
public int x;
public int y;
public float rotation;
}
to define the class called Ship, with integers x and y and a floating point number "rotation". The keyword public is a special keyword that means that other objects can mess with this value.
Within that class, you can add methods and subroutines, which do things to the ship's variables. For example, you can define this method within the definition of the Ship class:
public void Move(float amount)
{
X += Cos(Rotation) * amount;
Y += Sin(Rotation) * amount;
}

Once you have defined your Ship class, you can create a new instance of it, just like you would any other variable type (e.g. an integer or float). Then, later in the program, you can access its variables and call its subroutines. To reference a part of a class, first type the name you gave that particular instance of the object, then a period, and then the property you want to reference.
Ship ship = new Ship();
ship.rotation = Pi;
ship.Move(10);
Print(ship.x);
This piece of code creates a new instance of Ship, sets its rotation to Pi, moves it forward 10 pixels, and prints the ship's x-coordinate (which should now be -10).

Now, you might be asking: Why would I ever want to use this? There are two main reasons you would.
First, while it might be easier to manage one ship in low level programming, how about managing 100 of them? To track down all 300 variables, even in a list, would be unbearable, especially if you decided later that ships also need to have health or something. However, if you create a list of Ships, you can manage each ship individually.
Second, objects encapsulate things that you just don't want to manage, or want to protect somehow. For example, our Ship had a subroutine called Move on it to move the ship forward. Instead of having to remember sines and cosines every time a person wanted to move the ship, they could just set the rotation and movement amount and just say "Move". OOP also lets you hide variables that an object needs to know about, but not the rest of the game.

And objects have real-life applications as well, more so than in games. For example, you might want to create an object called CALCnet that manages calculator linking. By using this object, you don't have to worry about all of the little details and issues with CALCnet. All you have to do is start it up, shut it down, and tell it to send frames to people.

So, that's OOP 101. There is still a LOT more to the world of OOP, and I would be happy to share my knowledge.

EDIT: I realize that the sheer magnitude of this explanation might have scared you guys away. I hope I can be clearer and help you learn OOP.