<?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, 23 May 2013 01:35:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Using CLANG/scan-build for Static Analysis of the PHP Interpreter]]></title>
      <guid>http://www.phpdeveloper.org/news/17269</guid>
      <link>http://www.phpdeveloper.org/news/17269</link>
      <description><![CDATA[<p>
In a new post to his blog <i>Sebastian Bergmann</i> takes a quick look at <a href="http://sebastian-bergmann.de/archives/916-Using-CLANGscan-build-for-Static-Analysis-of-the-PHP-Interpreter.html">using a static analyzer</a>, <a href="http://clang.llvm.org/">clang</a> and scan-build, to analyze the PHP interpreter (specifically during the compile process).
</p>
<blockquote>
I have been tinkering with <a href="http://clang.llvm.org/">CLANG</a>'s <a href="http://clang-analyzer.llvm.org/">static analyzer</a> lately. This post summarizes how I installed LLVM and CLANG and performed the analysis of a build of the PHP interpreter.
</blockquote>
<p>
He includes all the commands (unix-based) to get the clang tools/libraries installed in the correct places as well as what to add to your $PATH to get the "scan-build" command to work with the make and make install parts of the PHP compile process.
</p>]]></description>
      <pubDate>Fri, 16 Dec 2011 09:48:07 -0600</pubDate>
    </item>
  </channel>
</rss>
