<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why we need abstract class in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-we-need-abstract-class/m-p/8922379#M1691716</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hiii,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;Classes which contain one or more abstract methods or abstract properties, such methods or properties do not provide implementation. These abstract methods or properties are implemented in the derived classes (Sub-classes).&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;Abstract classes does not create any instances to that class objects&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;We can define some common functionality in Abstract class (Super-class) and those can be used in derived classes (Sub classes).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you make normal class and now if you want some different logic for different company than when you change logic in original one than it will affect all the programs where you had used that class, Instead of that you just create class as a abstract and as per different company scenario you can create just implementation class which contain logic as per your scenario or if other functionality required than you can create just new method in your child class now you can say - WE CAN MAKE DIFFERENT classes for each scenario but if you want use re usability feature of OOPS than you should go with ABSTRACT CLASS so that it is easy to understand means just you reuse a ready made class by inheriting it and implementing your own logic as per requirement&amp;nbsp; .&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jul 2012 10:53:50 GMT</pubDate>
    <dc:creator>Aashish28</dc:creator>
    <dc:date>2012-07-19T10:53:50Z</dc:date>
    <item>
      <title>Why we need abstract class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-we-need-abstract-class/m-p/8922378#M1691715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN class="postbody"&gt;Hi experts,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="postbody"&gt;Why we need abstract class ??? we can also perform all the task from a simple class also...Looking for a solid answer .... &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="postbody"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="postbody"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000;"&gt;Moderator Message: Please search before posting.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: Suhas Saha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2012 10:22:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-we-need-abstract-class/m-p/8922378#M1691715</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-07-19T10:22:19Z</dc:date>
    </item>
    <item>
      <title>Re: Why we need abstract class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-we-need-abstract-class/m-p/8922379#M1691716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hiii,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;Classes which contain one or more abstract methods or abstract properties, such methods or properties do not provide implementation. These abstract methods or properties are implemented in the derived classes (Sub-classes).&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;Abstract classes does not create any instances to that class objects&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Arial;"&gt;We can define some common functionality in Abstract class (Super-class) and those can be used in derived classes (Sub classes).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you make normal class and now if you want some different logic for different company than when you change logic in original one than it will affect all the programs where you had used that class, Instead of that you just create class as a abstract and as per different company scenario you can create just implementation class which contain logic as per your scenario or if other functionality required than you can create just new method in your child class now you can say - WE CAN MAKE DIFFERENT classes for each scenario but if you want use re usability feature of OOPS than you should go with ABSTRACT CLASS so that it is easy to understand means just you reuse a ready made class by inheriting it and implementing your own logic as per requirement&amp;nbsp; .&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2012 10:53:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-we-need-abstract-class/m-p/8922379#M1691716</guid>
      <dc:creator>Aashish28</dc:creator>
      <dc:date>2012-07-19T10:53:50Z</dc:date>
    </item>
    <item>
      <title>Re: Why we need abstract class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/why-we-need-abstract-class/m-p/8922380#M1691717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Noufal ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; color: #575757;"&gt;Yes we know that we can perform all task from a simple class , but we still make use of abstract class. The very reason to this cannot be figured out easily because its a matter of choice or you may say its a situation , whether you want to or do not want to. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; color: #575757;"&gt;I prefer to make a&amp;nbsp; "skeleton" &lt;/SPAN&gt;(&lt;EM&gt;abstract&lt;/EM&gt;) &lt;SPAN style="font-size: 10pt; color: #575757;"&gt;and put it in different physical "body" which may work differently , but rather would I need that my invented skeleton should be workable ?....................i think NO, no use.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; color: #575757;"&gt;Lets talk in more simple ways , what is abstract class , its use ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: 1em; font-size: 14px; background-color: #ffffff; color: #000000; font-family: Arial, 'Liberation Sans', 'DejaVu Sans', sans-serif;"&gt;&lt;SPAN style="font-size: 10pt; color: #575757;"&gt;An abstract class is useful when you want to define part of the implementation of an object, but want to leave other parts up to the derived class. One key thing to remember about abstract classes is that they cannot be instantiated by themselves, because they typically lack a complete implementation as well as the fact that abstract keyword tells it can't be instantiated. Yes, you can supply dummy implementations, but why? The whole point is that abstracts are.. well.. abstract.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: 1em; font-size: 14px; background-color: #ffffff; color: #000000; font-family: Arial, 'Liberation Sans', 'DejaVu Sans', sans-serif;"&gt;&lt;SPAN style="font-size: 10pt; color: #575757;"&gt;Imagine you have a class Cat, and this class derives from a class Animal. There is no such thing as an Animal object, it's just a "type". You can't instantiate an Animal because there is no actual Animal in the real world, there are only creatures that are of the type Animal. You can treat different creatures as a common Animal type, but there can't exist a real Animal, it's just a concept.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: 1em; font-size: 14px; background-color: #ffffff; color: #000000; font-family: Arial, 'Liberation Sans', 'DejaVu Sans', sans-serif;"&gt;&lt;SPAN style="font-size: 10pt; color: #575757;"&gt;An Animal would be an abstract type, because the concept of the Animal is abstract. The same is true in software. You might have the concept of an object, such as a Stream. Is it a NetworkStream? A FileStream? A MemoryStream? Stream is just a concept.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: 1em; font-size: 14px; background-color: #ffffff; color: #000000; font-family: Arial, 'Liberation Sans', 'DejaVu Sans', sans-serif;"&gt;&lt;SPAN style="font-size: 10pt; color: #575757;"&gt;So , we can say an abstract is just as a concept , which is just being developed to be implemented by other .&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: 1em; font-size: 14px; background-color: #ffffff; color: #000000; font-family: Arial, 'Liberation Sans', 'DejaVu Sans', sans-serif;"&gt;Thanx &amp;amp; Regards ,&lt;/P&gt;&lt;P style="margin-bottom: 1em; font-size: 14px; background-color: #ffffff; color: #000000; font-family: Arial, 'Liberation Sans', 'DejaVu Sans', sans-serif;"&gt;Yogendra Bhaskar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jul 2012 11:09:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/why-we-need-abstract-class/m-p/8922380#M1691717</guid>
      <dc:creator>yogendra_bhaskar</dc:creator>
      <dc:date>2012-07-19T11:09:48Z</dc:date>
    </item>
  </channel>
</rss>

