<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 23 May 2013 11:35:43 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Liip Blog: PHPDoc Compilers and the @inheritdoc]]></title>
      <guid>http://www.phpdeveloper.org/news/16632</guid>
      <link>http://www.phpdeveloper.org/news/16632</link>
      <description><![CDATA[<p>
On the Liip blog there's <a href="http://blog.liip.ch/archive/2011/07/26/phpdoc-compilers-and-inheritdoc.html">a new post</a> that compares some of the popular PHPDocumentor-formatted comments parsers. They're looking specifically at the support for interfaces, not just the usual classes and methods.
</p>
<blockquote>
The interfaces define the standard and are extensively documented. The implementation was built by copying the interfaces and implementing the methods. Now we have the documentation comments duplicated, which is a pain to maintain if we clarify or change anything in the interfaces documentation. [...] In PHP, there is a couple of doc compilers. While they basically all follow the same syntax as Java uses, none of them gets everything right unfortunately. 
</blockquote>
<p>
The four covered are <a href="http://peej.github.com/phpdoctor/">PhpDoctor</a>, <a href="http://www.docblox-project.org/">DocBlox</a>, <a href="http://www.phpdoc.org/">PHPDoc</a> and <a href="http://www.stack.nl/~dimitri/doxygen/">Doxygen</a>. They look at things like namespace support, the inheritance information they generate and if it correctly uses the "@inheritDoc" tagging functionality.
</p>]]></description>
      <pubDate>Tue, 26 Jul 2011 09:29:06 -0500</pubDate>
    </item>
  </channel>
</rss>
