<?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, 24 May 2012 05:13:45 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Sameer Borate's Blog: Detecting duplicate code in PHP files]]></title>
      <guid>http://www.phpdeveloper.org/news/12300</guid>
      <link>http://www.phpdeveloper.org/news/12300</link>
      <description><![CDATA[<p>
On his blog today <i>Sameer</i> looks at <a href="http://www.codediesel.com/tools/detecting-duplicate-code-in-php-files/">a method for finding duplicate code</a> in your applications with the help of <a href="http://github.com/sebastianbergmann/phpcpd/tree/master">PHPCPD</a>.
</p>
<blockquote>
Duplicated code in projects is a frequent thing and also the one ripe for factoring out in a new class or function. Cut/Paste coding is a common development practice among programmers, a lot of which can lead to code size increase and maintenance nightmares. <a href="http://github.com/sebastianbergmann/phpcpd/tree/master">PHPCPD</a> (php copy paste detector) is a PEAR tool that makes it easier to detect duplicate code in php projects. Below is a short tutorial on the PHPCPD package.
</blockquote>
<p>
You can either install the tool via a PEAR channel or directly from the github site. Once its downloaded and extracted you can immediately run it on the subdirectory of your choice. He also includes a more extended example - a search on a minimum of 5 lines of 70 tokens found to trip the filter in finding cloned functionality.
</p>]]></description>
      <pubDate>Wed, 08 Apr 2009 11:16:17 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Quality Assurance Tools for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/12153</guid>
      <link>http://www.phpdeveloper.org/news/12153</link>
      <description><![CDATA[<p>
<i>Sebastian Bergmann</i> has <a href="http://sebastian-bergmann.de/archives/856-Quality-Assurance-Tools-for-PHP.html">a new post</a> that lists a few quality assurance testing tools you can use to ensure that you and your code are safe to make the jump to production.
</p>
<p>
He's <a href="http://www.flickr.com/photos/sebastian_bergmann/3356003644/">laid out a map</a> of the tools that can all interact to create a more robust environment for automatically building and testing your code. Here's his list:
</p>
<ul>
<li><a href="http://pear.php.net/package/PHP_CodeSniffer">PHP_CodeSniffer</a>
<li><a href="http://phpmd.org/">phpmd</a>
<li><a href="http://github.com/sebastianbergmann/phpcpd/">phpcpd</a>
<li><a href="http://pdepend.org/">PHP_Depend</a>
<li><a href="http://www.phpunit.de/">PHPUnit</a>
</ul>
<p>
The results of all of these tools running on your code is then fed into the <a href="http://cruisecontrol.sourceforge.net/">CruiseControl</a> instance and passed off to <a href="http://phpundercontrol.org/">phpUnderControl</a> for final deployment.
</p>]]></description>
      <pubDate>Tue, 17 Mar 2009 12:02:53 -0500</pubDate>
    </item>
  </channel>
</rss>

