<?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: Define local classes in function groups in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168979#M122602</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Max,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply, but I guess I didn't explain the question well.&lt;/P&gt;&lt;P&gt;I am well familiar with OO programing, and what is the advantage of using interfaces.&lt;/P&gt;&lt;P&gt;my concern is wether to define these classes globally (transaction SE24), or locally in function group(expose the class to the 'world' by global interface).&lt;/P&gt;&lt;P&gt;I heard that the ABAP class loader is working better if you define all classes in one function group (load all classes once), but I didn't see any formal guideline/documentation about it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Yaron.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Jan 2006 10:04:21 GMT</pubDate>
    <dc:creator>former_member205305</dc:creator>
    <dc:date>2006-01-10T10:04:21Z</dc:date>
    <item>
      <title>Define local classes in function groups</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168977#M122600</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 have seen in few code examples that programmers defined their classes as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Interfaces are defined globally i.e. under package-&amp;gt;class library-&amp;gt;interfaces. &lt;/P&gt;&lt;P&gt;2. implementing classes are defined locally under: package-&amp;gt;function group (as public local class in the function group). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is What is the advantage/disadvantage of it? &lt;/P&gt;&lt;P&gt;(beside encapsulation).&lt;/P&gt;&lt;P&gt;I heard that the class loader is working better in that way, is that right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Yaron&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2006 08:07:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168977#M122600</guid>
      <dc:creator>former_member205305</dc:creator>
      <dc:date>2006-01-10T08:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: Define local classes in function groups</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168978#M122601</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 is like an empty box, so only definition exists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The implemantation is locally done, so you can have several objects (class) have the same covering (methods, variables,...) but they are different.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you can have methods have the same interface, but make different actions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The BADI, for example, are based on this concept.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the standard there's only the call of a method of a interface, so I can link this interface to my class and implement the method inserting the code I need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2006 09:12:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168978#M122601</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-01-10T09:12:59Z</dc:date>
    </item>
    <item>
      <title>Re: Define local classes in function groups</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168979#M122602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Max,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply, but I guess I didn't explain the question well.&lt;/P&gt;&lt;P&gt;I am well familiar with OO programing, and what is the advantage of using interfaces.&lt;/P&gt;&lt;P&gt;my concern is wether to define these classes globally (transaction SE24), or locally in function group(expose the class to the 'world' by global interface).&lt;/P&gt;&lt;P&gt;I heard that the ABAP class loader is working better if you define all classes in one function group (load all classes once), but I didn't see any formal guideline/documentation about it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Yaron.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2006 10:04:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168979#M122602</guid>
      <dc:creator>former_member205305</dc:creator>
      <dc:date>2006-01-10T10:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: Define local classes in function groups</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168980#M122603</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;excuse me I miserunderstood.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Perhaps it's true I don't know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think the different is the SE24 is a library, so it's the tool arranged to analyze all class components you can need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't think it's easier to analyze an include (function group) where the class is defined and implemented.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You shuold measure the time in order to load the class for both case, but probably the different isn't meaningful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should consider that ABAP wasn't OO language, but it was adapted for OO, and so the most ABAP developer weren't used to use OO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you should define a class as local class if it's your own class.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: max bianchi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2006 10:29:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/define-local-classes-in-function-groups/m-p/1168980#M122603</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-01-10T10:29:34Z</dc:date>
    </item>
  </channel>
</rss>

