<?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>Tue, 18 Jun 2013 20:02:57 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPMaster.com: Introduction to PhpDoc]]></title>
      <guid>http://www.phpdeveloper.org/news/17370</guid>
      <link>http://www.phpdeveloper.org/news/17370</link>
      <description><![CDATA[<p>
On PHPMaster.com today there's a new post from <i>Moshe Teutsch</i> about <a href="http://phpmaster.com/introduction-to-phpdoc/">working with docblock comments</a> in PHP scripts and how to use the <a href="http://phpdoc.org">phpDocumentor</a> tool to generate the documentation from them.
</p>
<blockquote>
If you've ever tried to read code written by someone other than yourself (who hasn't?), you know it can be a daunting task. [...] PhpDoc, short for PhpDocumentor, is a powerful tool that allows you to easily document your code via specially formatted comments. [...] By using PhpDoc, you can make it easy for others (and yourself) to understand your code - weeks, months, and even years after you've written it.
</blockquote>
<p>
He introduces the concept of "docblocks" and includes several examples of how to comment things like packages, files, classes and functions/methods. Finally, he wraps up the post with an example of using the "phpdoc" command to run phpDocumentor and build the docs. In the comments, another tool is also suggested - <a href="http://docblox-project.org/">DocBlox</a>, a project that still parses the same docbloc syntax but does it in a much more memory efficient way (and is an actively maintained project).
</p>]]></description>
      <pubDate>Tue, 10 Jan 2012 10:07:26 -0600</pubDate>
    </item>
  </channel>
</rss>
