<?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, 21 May 2013 23:55:31 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Project: PHPHint.org - Online PHP Code Analysis]]></title>
      <guid>http://www.phpdeveloper.org/news/18332</guid>
      <link>http://www.phpdeveloper.org/news/18332</link>
      <description><![CDATA[<p>
<i>Klaus Silveira</i> has submitted a project he's come up with to help PHP developers detect problems in their code via a web-based application - <a href="http://phphint.org">PHPHint.org</a>.
</p>
<blockquote>
<p>
PHPHint is a community-driven, quick and easy to use, online tool that analyzes your PHP code and looks for potential errors, lack of <a href="http://paul-m-jones.com/archives/2420">best practices</a> and <a href="http://en.wikipedia.org/wiki/Code_smell">code smell</a>. It also allows you to clean your code automagically.
</p>
<p>
It was created to spread the work about the PSR standards and the PHP-FIG group, the importance of getting rid of code smell and applying to standards.
</p>
</blockquote>
<p>
Since it is an open source project, you can <a href="https://github.com/klaussilveira/PHPHint">help contribute</a> if you'd like to see improvements to the service. It's great that it takes the relatively new PSR standards (<a href="https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md">PSR-1</a> & <a href="https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md">PSR-2</a>) into account when analyzing the code too.
</p>]]></description>
      <pubDate>Wed, 08 Aug 2012 10:18:59 -0500</pubDate>
    </item>
  </channel>
</rss>
