<?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: Documentation for redefined methods? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837103#M1317394</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;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; I'm surprised no one has views on this. Do you all leave your methods undocumented?&lt;/P&gt;&lt;P&gt;&amp;gt; I have decided to put a comment for each redefined method in the class documentation of the subclass. Though unsatisfactory, that is the best I can think of.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; -- Sebastian&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I'm designing a generic class for use by other programmers, then I might use the documentation.  Otherwise, I document in the method.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my experience that's where most developers look first.  There's so many undocumented methods (and other objects) in SAP, that the thought to check it is usually a last resort!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Jun 2009 14:31:20 GMT</pubDate>
    <dc:creator>matt</dc:creator>
    <dc:date>2009-06-22T14:31:20Z</dc:date>
    <item>
      <title>Documentation for redefined methods?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837099#M1317390</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I seem not to be able to create documentation for redefined methods. In se80, the method docs only open in read-ony mode and display the documentation from the superclass.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because the whole point of redefinitionis to add functionality, which of course should be documented, I am very unhappy with this. What do you recommend to do? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- Sebastian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2009 11:53:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837099#M1317390</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-06-18T11:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation for redefined methods?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837100#M1317391</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm surprised no one has views on this. Do you all leave your methods undocumented?&lt;/P&gt;&lt;P&gt;I have decided to put a comment for each redefined method in the class documentation of the subclass. Though unsatisfactory, that is the best I can think of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- Sebastian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 21 Jun 2009 11:38:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837100#M1317391</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-06-21T11:38:46Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation for redefined methods?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837101#M1317392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This message was moderated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jun 2009 06:33:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837101#M1317392</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-06-22T06:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation for redefined methods?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837102#M1317393</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good Finding Sebastian. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More over to the class documentation, you may also put the documentation as the comment in the beginning of the Redefined method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest you to raise it to OSS to let SAP know about the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naimesh Patel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jun 2009 13:53:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837102#M1317393</guid>
      <dc:creator>naimesh_patel</dc:creator>
      <dc:date>2009-06-22T13:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation for redefined methods?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837103#M1317394</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;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; I'm surprised no one has views on this. Do you all leave your methods undocumented?&lt;/P&gt;&lt;P&gt;&amp;gt; I have decided to put a comment for each redefined method in the class documentation of the subclass. Though unsatisfactory, that is the best I can think of.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; -- Sebastian&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I'm designing a generic class for use by other programmers, then I might use the documentation.  Otherwise, I document in the method.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my experience that's where most developers look first.  There's so many undocumented methods (and other objects) in SAP, that the thought to check it is usually a last resort!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jun 2009 14:31:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837103#M1317394</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2009-06-22T14:31:20Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation for redefined methods?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837104#M1317395</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From the replies I gather that there no one has a satisfactory solution. I am now documenting the added functionality in the ABAP code, and add a caveat to the superclass's method documentation to check the coding for further info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my opinion this is a really bad situation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Nov 2009 12:56:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/documentation-for-redefined-methods/m-p/5837104#M1317395</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-10T12:56:54Z</dc:date>
    </item>
  </channel>
</rss>

