<?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>Fri, 24 May 2013 03:04:46 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[William Candillon's Blog: PHP source code analysis: PHPCompiler versus Yaxx]]></title>
      <guid>http://www.phpdeveloper.org/news/5628</guid>
      <link>http://www.phpdeveloper.org/news/5628</link>
      <description><![CDATA[<p>
From <i>William Candillon</i> today on the "Yet another PHP blog", there's <a href="http://wcandillon.blogspot.com/2006/06/php-source-code-analysis-phpcompiler_19.html">his comparison</a> at the source coude level of PHPCompiler versus Yaxx.
</p>
<blockquote>
<p>
Before I choose <a href="http://wcandillon.blogspot.com/2006/06/using-xml-representations-of-php-parse.html">yaxx</a> and XML tools for code source transformation, I looked very attentively the <a href="http://www.phpcompiler.org/">phpCompiler project</a>.
</p>
<p>
The main goal of phpCompiler is to translate PHP code directly into Linux assembly code (and they are apparently very close to it).
</p>
</blockquote>
<p>
He <a href="http://wcandillon.blogspot.com/2006/06/php-source-code-analysis-phpcompiler_19.html">mentions</a>, though, that phpCompiler just doesn't fit what he's trying to do. He needs things like portability between platforms and a simple way to extend the PHP lexer and grammer for phpAspect. Unfortunately, phpCompiler either doesn't allow these or just makes them too difficult. He makes his choice for his situation - <a href="http://wcandillon.blogspot.com/2006/06/using-xml-representations-of-php-parse.html">Yaxx</a>
</p>]]></description>
      <pubDate>Tue, 20 Jun 2006 05:48:27 -0500</pubDate>
    </item>
  </channel>
</rss>
