<?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>Wed, 19 Jun 2013 13:55:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Project: Kint - Advanced Output for Debugging ]]></title>
      <guid>http://www.phpdeveloper.org/news/15799</guid>
      <link>http://www.phpdeveloper.org/news/15799</link>
      <description><![CDATA[<p>
One of the more difficult parts of development is debugging. Any tool that can help make your bug finding life simpler can be valuable. <i>Raveren</i> has submitted a new tool he's developed to make outputting your debugging information more useful - <a href="http://code.google.com/p/kint/">Kint</a>.
</p>
<blockquote>
 It's basically a heavily improved var_dump and debug_backtrace version with some advanced behind the scenes action. The features description is in the google code page: <a href="http://code.google.com/p/kint/">http://code.google.com/p/kint/</a> but the interesting part is that this is the only dump tool, that can display the name of the dumped variable as well as use modifiers on the calling function.
</blockquote>
<p>
The flow is traced back to its origin class/script and a token parser is used to find where the value was created. You can see a sample of how to use it over on its <a href="http://code.google.com/p/kint/">Google Code</a> page. This also includes screenshots of the output and the configuration values you can set for things like a display path callback and the maximum number of levels to traverse through. You can download the current version <a href="http://code.google.com/p/kint/downloads/detail?name=Kint-v1.rar">here</a>.
</p>]]></description>
      <pubDate>Tue, 25 Jan 2011 08:16:09 -0600</pubDate>
    </item>
  </channel>
</rss>
