<?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: Class Definition &amp; Implementation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-definition-implementation/m-p/4802893#M1124512</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Suresh Reddy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main intention behind this design is &lt;/P&gt;&lt;P&gt;" to differentiate the class definition and implementation clearly ."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even if you have a chance to including both  class definition and implementation in same structure, it is difficult to differentiate  these things in lengthy implementation classes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Prasad GVK.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Dec 2008 16:08:01 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-12-02T16:08:01Z</dc:date>
    <item>
      <title>Class Definition &amp; Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-definition-implementation/m-p/4802891#M1124510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;  In JAVA or Other OOP languages the class definition &amp;amp; implementation are doing within the same task i.e with in the class only they are defining &amp;amp; implementing.But when it comes to ABAP the definition part &amp;amp; implementation part of a class are divided into 2 tasks. Why they are designed like that?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Nov 2008 16:08:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/class-definition-implementation/m-p/4802891#M1124510</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-11-29T16:08:51Z</dc:date>
    </item>
    <item>
      <title>Re: Class Definition &amp; Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-definition-implementation/m-p/4802892#M1124511</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;i do not know whether you know the language of c++ or not, in c++ , we can define  and implement the&lt;/P&gt;&lt;P&gt;class separately or implement the class within the definition of the class, but in java we do not do like this. and in abap , we must do it separately. i think the design is not that important, and the key point to us is what we must follow the principle of the oops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;that is my understanding about this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Dec 2008 01:38:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/class-definition-implementation/m-p/4802892#M1124511</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-01T01:38:25Z</dc:date>
    </item>
    <item>
      <title>Re: Class Definition &amp; Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-definition-implementation/m-p/4802893#M1124512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Suresh Reddy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main intention behind this design is &lt;/P&gt;&lt;P&gt;" to differentiate the class definition and implementation clearly ."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even if you have a chance to including both  class definition and implementation in same structure, it is difficult to differentiate  these things in lengthy implementation classes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Prasad GVK.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Dec 2008 16:08:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/class-definition-implementation/m-p/4802893#M1124512</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-02T16:08:01Z</dc:date>
    </item>
  </channel>
</rss>

