Regarding abstract class

Hi Friends,

My Question is in which scenario we can use this design?

When you don't allow anyone to instantiate this class, but you want to have implementation code in it ... and may or may not have abstract method.

We use abstract class when we want to force implementing class to implement abstract class methods.

Dejan Miler wrote:We use abstract class when we want to force implementing class to implement abstract class methods.

Wrong, an abstract class doesn't need to have any abstract methods...

I know that
The main purpose of creating abstract class is when we want to make that it cannot be initialized and to force
first non abstract class who extends that abstract class to implement all abstract method from that abstract class.

Lorand Komaromi wrote:

Dejan Miler wrote:We use abstract class when we want to force implementing class to implement abstract class methods.

Wrong, an abstract class doesn't need to have any abstract methods...

Yes , Dejan Miler statement is not for abstract class, it is actually more appropriate for interface, all method in interface is implicitly public abstract.

we declare a class abstract for two reasons

1)to prevent creting objects
2)if the class has any abstract methods

if the class has abstract methods then the class that inherits it must implemet the methods that are declared abstract or declare itself abstract....
Hence if you want to force a sub class to implement the super class method the method must be declared abstract and the class abstract

abstract class a{

abstract void put(){}
void get(){}
}
class b extends a{
/*it must override the abstract methods put of class a but no need to override get() method*/
}

abstract classes can contain fields that are not static and final and also implemented methods

but if the abstract class contains only abstract methods then it the same as a interface

You are fast

Yes , Dejan Miler statement is not for abstract class, it is actually more appropriate for interface, all method in interface is implicitly public abstract.

I agree that statment is more appropriate for interface.
But we all know that we can have abstract class with methods who are all abstract.
So if all methods in abstract classes are abstract we can say that that class is very similar to interface.
And we all know that interface is 100% abstract and class can or do not need to be 100% abstract.

we declare a class abstract for two reasons

1)to prevent creting objects
2)if the class has any abstract methods

if the class has abstract methods then the class that inherits it must implemet the methods that are declared abstract or declare itself abstract....
Hence if you want to force a sub class to implement the super class method the method must be declared abstract and the class abstract

Yes, you are right, this is the rules/specifications.

Now, the important point is, if you only have abstract method in the abstract class, you should consider using interface.

I agree that statment is more appropriate for interface.
But we all know that we can have abstract class with methods who are all abstract.
So if all methods in abstract classes are abstract we can say that that class is very similar to interface.
And we all know that interface is 100% abstract and class can or do not need to be 100% abstract.

Yes, you are right. What you mentioned is still rules/specification
It is similar and it is not similar, it will cost you in your future of design.
If you have 100% abstract method, please consider using interface, code to interface is a good practice.
And it will help you in the future, for example on multiple inheritance. Also for design pattern , because software in real world is tend to grows and tend to have mid course changes.

Here I had just try to defend my honor.
And of course that i will use interface rather then abstract class

Hi Friends,
Thanks For Your Replies.

But one more doubt, suppose if i will add two more concrete methods(like m4() and m5())to my abstract class,will it break the clients code(who uses my code)?

I do not see any reason at all how that can brake you code

But one more doubt, suppose if i will add two more concrete methods(like m4() and m5())to my abstract class,will it break the clients code(who uses my code)?

To answer your question , I will assume that you are mentioning the subclass that extends your abstract class.

By adding concrete methods to your abstract class , it won't break in term of code ... but be careful of your design, all the subclasses inherited from here will have those two methods, so you have to consider carefully when changing a parent class, it will break the purpose of the subclass (means the cohesiveness or in general term its abstraction level).