<?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: Diff between interface and Abstract class in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784285#M337855</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sagar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An abstract class can have methods containing "default" coding that is inherited to sub-classes. In contrast, methods of an interface never have any coding.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With an abstract class you can deliver a "sample" or "default" implementation of the methods. This is not possible using interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 03 Jan 2007 14:00:43 GMT</pubDate>
    <dc:creator>uwe_schieferstein</dc:creator>
    <dc:date>2007-01-03T14:00:43Z</dc:date>
    <item>
      <title>Diff between interface and Abstract class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784282#M337852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi to all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  I am woking on OOP in ABAP .Could any one can tell the difference between interface and abstract class.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; thanks in advance .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2007 13:50:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784282#M337852</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-03T13:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: Diff between interface and Abstract class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784283#M337853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sagar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interface is an pure abstact class. All methods under this class are abstract.The class which implements this interface will provide a implementation to this method&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have one of the method in your class is abstract then the class will be abstract. You can not create any instacne for abstract classes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vinay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2007 13:58:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784283#M337853</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-03T13:58:53Z</dc:date>
    </item>
    <item>
      <title>Re: Diff between interface and Abstract class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784284#M337854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Taken from help..........&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;i&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces are independent structures that allow you to enhance the class-specific public points of contact by implementing them in classes. Different classes that implement the same interface can all be addressed in the same way. Interfaces are the basis for polymorphism in classes, because they allow a single interface method to behave differently in different classes. Interface references allow users to address different classes in the same manner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/i&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;i&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;... ABSTRACT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;A class defined as ABSTRACT cannot be instantiated, that is, you cannot use CREATE OBJECT with reference to the class. Instead, you can only address the class using its static components or its subclasses. The major purpose of an abstract class is to serve as a template for subclasses. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a class contains abstract methods, that is, method declarations with the ABSTRACT addition, the whole class must also be abstract (that is, have the ABSTRACT addition), since a class may not be instantiated if it has unimplemented methods. Equally, if a subclass does not implement all of the abstract methods of its superclasses, it must itself declare them abstract. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;CLASS C1 DEFINITION  ABSTRACT. &lt;/P&gt;&lt;P&gt;  ... &lt;/P&gt;&lt;P&gt;ENDCLASS. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CLASS C2 DEFINITION INHERITING FROM C1. &lt;/P&gt;&lt;P&gt;  ... &lt;/P&gt;&lt;P&gt;ENDCLASS. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA CREF TYPE REF TO C1. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  CREATE OBJECT CREF TYPE C2. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Class C1 cannot be instantiated. However, the reference in the reference variable cref, defined with reference to class C1 can point to instances of the subclasses of C1 if these can be instantiated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/i&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2007 14:00:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784284#M337854</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2007-01-03T14:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: Diff between interface and Abstract class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784285#M337855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sagar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An abstract class can have methods containing "default" coding that is inherited to sub-classes. In contrast, methods of an interface never have any coding.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With an abstract class you can deliver a "sample" or "default" implementation of the methods. This is not possible using interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2007 14:00:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784285#M337855</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2007-01-03T14:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: Diff between interface and Abstract class</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784286#M337856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sagar,&lt;/P&gt;&lt;P&gt;like Uwe told one basic difference is that you may provide some methods with an abstract class but not with an interface. The unique feature of interfaces is that you may implement several ones while abstract classes are limited to one inheritance hierarchy.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Jan 2007 17:14:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/diff-between-interface-and-abstract-class/m-p/1784286#M337856</guid>
      <dc:creator>former_member183804</dc:creator>
      <dc:date>2007-01-04T17:14:50Z</dc:date>
    </item>
  </channel>
</rss>

