<?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: private section in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213137#M766024</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why do you answer this thread twice?  Didn't you notice your original answer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Dec 2007 20:56:17 GMT</pubDate>
    <dc:creator>matt</dc:creator>
    <dc:date>2007-12-27T20:56:17Z</dc:date>
    <item>
      <title>private section</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213131#M766018</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why use private section of a local class?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Dec 2007 09:12:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213131#M766018</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-23T09:12:27Z</dc:date>
    </item>
    <item>
      <title>Re: private section</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213132#M766019</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;To PROTECT the data to acess the data from out side classes &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw70/helpdata/en/c3/225b6554f411d194a60000e8353423/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw70/helpdata/en/c3/225b6554f411d194a60000e8353423/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Dec 2007 12:48:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213132#M766019</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-23T12:48:24Z</dc:date>
    </item>
    <item>
      <title>Re: private section</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213133#M766020</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Naresh is right, but perhaps you think it a little odd to have a private section in a local class, seeing as the local class can't be accessed outside the program anyway.  The reason for doing it, is data encapsulation.  By being specific about what data can be used under what circumstances, you have a better defined data model, and so you reduce the scope for error.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While you may be well aware of how your variables and methods should be used, the programmer who maintains your program in two years time may not be.  By using good encapsulation, you prevent him from making some errors.  If  an attribute is private, he can't access it outside the class.  If he decides to make it public, he can of course just change the class - but he has to do it deliberately.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Defining variables and methods with the correct scope is vital to writing good programs.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Dec 2007 05:22:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213133#M766020</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2007-12-24T05:22:07Z</dc:date>
    </item>
    <item>
      <title>Re: private section</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213134#M766021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Soman,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we need to declare attributes in a local class with in a private section&lt;/P&gt;&lt;P&gt;to avoid access by others class means only objects of that class can access it.&lt;/P&gt;&lt;P&gt;For Ex. In a company some documents are private and confidencial only employee can see it. same way only objects of that calss can acess private objects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you are going with inheritance we need decalre the attributes in a public section so that inherited class can access it. you can also use Protedted class wich can be access by inherited class&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Kindly Award Points If You Find The Reply Helpful&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Chaitanya.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Dec 2007 11:30:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213134#M766021</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-26T11:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: private section</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213135#M766022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;gt; Hi Soman,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; if you are going with inheritance we need decalre the attributes in a public section so that inherited class can access it. you can also use Protedted class wich can be access by inherited class&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you declare attributes that are to be inherited you should use protected.  You should only use public if access is required outside of the class.  Public access is always the LAST choice, not the first.&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, 26 Dec 2007 12:15:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213135#M766022</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2007-12-26T12:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: private section</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213136#M766023</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;To secre the data with in the class and not to access from out side the class &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The private components of the superclass are not visible though they exist in the subclass. You can declare private components in a subclass that have the same names as private components of the superclass. It is seen that each class works with its own private components. The another point that we note is that methods which a subclass inherits from a superclass use the private attributes of the superclass and not any private components of the subclass with the same names.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Dec 2007 06:14:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213136#M766023</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-27T06:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: private section</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213137#M766024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why do you answer this thread twice?  Didn't you notice your original answer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Dec 2007 20:56:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213137#M766024</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2007-12-27T20:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: private section</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213138#M766025</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;he is not closing thread so i am giving him a clear information about this&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2007 04:43:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/private-section/m-p/3213138#M766025</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-28T04:43:43Z</dc:date>
    </item>
  </channel>
</rss>

