<?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: Where to use OOPs in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/where-to-use-oops/m-p/5699999#M1294799</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use OOPs everywhere.  Correctly used, it will lead to: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a) Better program design&lt;/P&gt;&lt;P&gt;b) Programs that are easier to maintain&lt;/P&gt;&lt;P&gt;c) Programs that are cheaper to maintain&lt;/P&gt;&lt;P&gt;d) Programs that are easier to enhance&lt;/P&gt;&lt;P&gt;e) Programs that are cheaper to enhance&lt;/P&gt;&lt;P&gt;f) Programs that can be changed with affecting stability&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Part of this is because certain program practices - like typing, no header line tables - are enforced. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I now use non-OOPs only where strictly necessary.  And even then, I link to classes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 May 2009 05:43:03 GMT</pubDate>
    <dc:creator>matt</dc:creator>
    <dc:date>2009-05-27T05:43:03Z</dc:date>
    <item>
      <title>Where to use OOPs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/where-to-use-oops/m-p/5699998#M1294798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have done Object Oriented Programming for the purpose of ALV, and BADIs,&lt;/P&gt;&lt;P&gt;where else would OOPs cocenpts be used in ABAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any reason for using OOPs concept, where the same work can be done with normal regular programming.&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;Vinay.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2009 01:17:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/where-to-use-oops/m-p/5699998#M1294798</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-27T01:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: Where to use OOPs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/where-to-use-oops/m-p/5699999#M1294799</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use OOPs everywhere.  Correctly used, it will lead to: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a) Better program design&lt;/P&gt;&lt;P&gt;b) Programs that are easier to maintain&lt;/P&gt;&lt;P&gt;c) Programs that are cheaper to maintain&lt;/P&gt;&lt;P&gt;d) Programs that are easier to enhance&lt;/P&gt;&lt;P&gt;e) Programs that are cheaper to enhance&lt;/P&gt;&lt;P&gt;f) Programs that can be changed with affecting stability&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Part of this is because certain program practices - like typing, no header line tables - are enforced. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I now use non-OOPs only where strictly necessary.  And even then, I link to classes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2009 05:43:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/where-to-use-oops/m-p/5699999#M1294799</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2009-05-27T05:43:03Z</dc:date>
    </item>
  </channel>
</rss>

