[venuwin]

Hi,

I and my friend yesterday were discussing about a project in his company that was doomed.

The reason given by the client for the decision was that " Your developers have coded java in a procedural way and not in an Object oriented way".

I am not so clear on this. Could someone tell with few examples(or some URLs) the difference between Procedural Java and OOPS style java?


Thanks
Venu

[Ovda8aO]

Can Tell the OOPS with Linux operation ? What's up to OOPS ? The subjects to OOPS data structure of here doing.

[venuwin]

not able to understand what you are trying to convey

[jwenting]

which shows clearly that your customer was correct in his assertion that the project is doomed.
Utter incompetence of the people manning the project (which your ignorance indicates beyond doubt) is a guarantee of that.

[Trollhorn]

Lesson: Classes and Objects (The Java™ Tutorials > Learning the Java Language)

Lesson: Interfaces and Inheritance (The Java™ Tutorials > Learning the Java Language)

This should give you an idea about OOP in Java...

[santoro63]

OOP is more than knowing about classes, interfaces, inheritance and polymorphism. It's also about building your system in an object oriented way and frankly, it takes some experience and time to "get it."

Some signs that you built procedural code using Java:

1. Lots of "util" or "helper" classes
2. Lots of static methods and fields in your code
3. Lots of switch statements
4. Lots of singletons (a.k.a., global variables in disguise)

And these are just a few.

[eriksensei]

@jwenting: I don't believe venuwin said it was at *his* company, so what you refer to as his 'ignorance' has no bearing on the project he was talking about. Besides, if it troubles you so, why not provide some examples? Might be a tad more helpful

@venuwin: Some tell-tale proceduralisms would be lots of 'instanceof' checks in the code (e.g. the switch statements santoro63 talks about). This indicates the developer is not taking advantage of Java's OO features such as inheritance, which would allow the JVM to invoke ('dispatch') the appropriate operations on objects automatically, as opposed to having the code explicitly check for object types and calling. E.g.:

// procedural (not so pretty)
Animal animal = new Mouse();
if (animal instanceof Mouse) {
  System.out.println("cheese");
} else if (animal instanceof Cat) {
  System.out.println("catnip");
}

As opposed to:

class Animal {
  public abstract String getFood();
}

class Mouse extends Animal {
  @Override
  public void getFood() { System.out.println("cheese"); }
}

class Cat extends Animal {
  @Override
  public void getFood() { System.out.println("catnip"); }
}

// now the JVM can automatically decide what
// method to invoke 
Animal animal = new Cat();
animal.getFood();

Google for OO, instanceof, dispatch, etc. Hope this helps!

Toedeloe,
Erik

[Trollhorn]

@Santaro63 Of course OOP is not only about classes, interfaces and so on, and I agree with you that it takes a lot of time to understand the really important things... I just wanted to provide a good reference to start with...

[greannak]

It's also about building your system in an object oriented way and frankly, it takes some experience and time to "get it."