<?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: interface in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2797496#M653087</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces only describe the external point of contact of a class (protocols), they do not contain any implementation. &lt;/P&gt;&lt;P&gt;Interfaces are usually defined by a user. The user describes in the interface which services (technical and semantic) it needs in order to carry out a task.&lt;/P&gt;&lt;P&gt; The user never actually knows the providers of these services, but communicates with them through the interface.&lt;/P&gt;&lt;P&gt; In this way the user is protected from actual implementations and can work in the same way with different classes/objects, as long as they provide the services required. This is known as polymorphism with interfaces.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Sep 2007 04:19:49 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-11T04:19:49Z</dc:date>
    <item>
      <title>interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2797495#M653086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi explain me the interface concept&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Sep 2007 14:54:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2797495#M653086</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-10T14:54:19Z</dc:date>
    </item>
    <item>
      <title>Re: interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2797496#M653087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces only describe the external point of contact of a class (protocols), they do not contain any implementation. &lt;/P&gt;&lt;P&gt;Interfaces are usually defined by a user. The user describes in the interface which services (technical and semantic) it needs in order to carry out a task.&lt;/P&gt;&lt;P&gt; The user never actually knows the providers of these services, but communicates with them through the interface.&lt;/P&gt;&lt;P&gt; In this way the user is protected from actual implementations and can work in the same way with different classes/objects, as long as they provide the services required. This is known as polymorphism with interfaces.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Sep 2007 04:19:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2797496#M653087</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-11T04:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2797497#M653088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interfaces&lt;/P&gt;&lt;P&gt;In ABAP interfaces are implemented in addition to, and independently of classes. An interface only has a declaration part, &lt;/P&gt;&lt;P&gt;and do not have visibility sections. Components (Attributes, methods, constants, types) can be defined the same way as in classes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·                Interfaces are listed in the definition part lof the class, and must always be in the PUBLIC SECTION.&lt;/P&gt;&lt;P&gt;·                Operations defined in the interface atre impemented as methods of the class. All methods of the interface&lt;/P&gt;&lt;P&gt;must be present in the  implementation part of the class.&lt;/P&gt;&lt;P&gt;·                Attributes, events, constants and types defined in the interface are automatically available to the class &lt;/P&gt;&lt;P&gt;carrying out the implementation.&lt;/P&gt;&lt;P&gt;·                Interface components are addressed in the class by display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if helpfull&lt;/P&gt;&lt;P&gt;rgds,&lt;/P&gt;&lt;P&gt;Prajith&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Sep 2007 07:45:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2797497#M653088</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-11T07:45:26Z</dc:date>
    </item>
  </channel>
</rss>

