<?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: ABAP Doc for Method implementation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116115#M1973913</link>
    <description>&lt;P&gt;Write the ABAP-Doc comment in the interface-definition of the method.&lt;/P&gt;&lt;P&gt;e.g.&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt; "! Writing Hello
 methods write_hello.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Every implementation of this interface method should write "Hello" and that's the reason why there is no need of documentation for every implementation. How the method implementation is doing his job isn't important for the comment.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Nov 2019 10:43:04 GMT</pubDate>
    <dc:creator>ascm</dc:creator>
    <dc:date>2019-11-28T10:43:04Z</dc:date>
    <item>
      <title>ABAP Doc for Method implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116114#M1973912</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
  &lt;P&gt;currently, it seems to me that ABAP Doc Documentation can only be created on the level of method definition. &lt;/P&gt;
  &lt;P&gt;But how does that apply to the concept of object orientation?&lt;/P&gt;
  &lt;P&gt;E.g. if the method is defined in an interface and there are multiple implementations. In this case it would make sense to create a method implementation documentation using ABAP Doc, but this is not possible, or is it?&lt;/P&gt;
  &lt;P&gt;Another problem is the documentation of redefined methods in inhertited classes, same as a above. ABAP Doc can only be created once for the original method definition.&lt;/P&gt;
  &lt;P&gt;Gruß,&lt;/P&gt;
  &lt;P&gt;Sebastian&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 09:29:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116114#M1973912</guid>
      <dc:creator>koitka</dc:creator>
      <dc:date>2019-11-28T09:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Doc for Method implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116115#M1973913</link>
      <description>&lt;P&gt;Write the ABAP-Doc comment in the interface-definition of the method.&lt;/P&gt;&lt;P&gt;e.g.&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt; "! Writing Hello
 methods write_hello.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Every implementation of this interface method should write "Hello" and that's the reason why there is no need of documentation for every implementation. How the method implementation is doing his job isn't important for the comment.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 10:43:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116115#M1973913</guid>
      <dc:creator>ascm</dc:creator>
      <dc:date>2019-11-28T10:43:04Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Doc for Method implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116116#M1973914</link>
      <description>&lt;P&gt;This does not allow detailed documentation. E.g. 2 classes are implementing the interface method, how to describe the difference? How should the caller decide wich one to choose if both share the same documentation. I think this is a limitation.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2019 09:51:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116116#M1973914</guid>
      <dc:creator>koitka</dc:creator>
      <dc:date>2019-12-02T09:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Doc for Method implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116117#M1973915</link>
      <description>&lt;P&gt;Agree with your response to Andrea's answer.&lt;BR /&gt;I can think of using Alias in which you can give a meaningful name to your interface method.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2019 13:52:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116117#M1973915</guid>
      <dc:creator>rajad</dc:creator>
      <dc:date>2019-12-02T13:52:41Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Doc for Method implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116118#M1973916</link>
      <description>&lt;P&gt;How does Alias help? It is not possible to add an ABAP Doc Documentation to an alias. &lt;/P&gt;&lt;P&gt;If it was possible, this could at least be a workaround...&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2019 10:15:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-doc-for-method-implementation/m-p/12116118#M1973916</guid>
      <dc:creator>koitka</dc:creator>
      <dc:date>2019-12-04T10:15:54Z</dc:date>
    </item>
  </channel>
</rss>

