<?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 04:27:29 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPBuilder.com: Four Sane Solutions for PHP Debugging]]></title>
      <guid>http://www.phpdeveloper.org/news/15388</guid>
      <link>http://www.phpdeveloper.org/news/15388</link>
      <description><![CDATA[<p>
On PHPBuilder.com today there's a new article from <i>Jason Gilmore</i> sharing what he calls "four sane solutions" to help you debug your PHP applications better than just an <a href="http://php.net/echo">echo</a> or <a href="http://php.net/var_dump">var_dump</a>.
</p>
<blockquote>
Few tasks are more tedious and frustrating than debugging a Web application. [...] Fortunately, PHP developers have a number of powerful debugging solutions at their disposal. Whether you're merely inspecting array contents or attempting to determine the status of an Ajax-driven POST response, these four solutions are guaranteed to have an immediate impact on your productivity.
</blockquote>
<p>
His four solutions involve changing the error reporting level on your development environment higher than production to catch issues that might slip through unnoticed, using <a href="http://xdebug.org">XDebug</a>, integrating <a href="http://www.firephp.org/">FirePHP</a> and using <a href="http://www.webopedia.com/TERM/T/test_driven_development.html">test-driven development</a> to be sure things work from the outset.
</p>]]></description>
      <pubDate>Fri, 05 Nov 2010 08:41:28 -0500</pubDate>
    </item>
  </channel>
</rss>
