<?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 06:38:31 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Joshua Thompson's Blog: A Plugabble Preprocessor For PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/10942</guid>
      <link>http://www.phpdeveloper.org/news/10942</link>
      <description><![CDATA[<p>
<i>Joshua Thompson</i>, inspired by <a href="http://c7y.phparch.com/c/entry/1/art,practical_uses_tokenizer">another blog post</a> on a use for the PHP tokenizer, has started off on a new project to expand on one of the examples - a preprocessor.
</p>
<blockquote>
It makes a lot of sense for the library developer. They could easily create multiple versions of their code depending on PHP version, target platform, backend database, etc. So I started working on my own implementation of a preprocessor with the goal of making it easy to add plugins for additional functionality. It was during the construction of the core of the preprocessor, that it hit me: why can't we implement new language features in the preprocessor.
</blockquote>
<p>
As a result, he's created his first version of <a href="http://personal.schmalls.com/downloads/ppp-0.1.0-dev.tar.bz2">PPP - PPP PHP PreProcessor</a> (yes, recursive). It's a starting point that has a plugin for traits handling and a soon to come plugin to reduce the need for namespaces.
</p>]]></description>
      <pubDate>Tue, 02 Sep 2008 09:34:31 -0500</pubDate>
    </item>
  </channel>
</rss>
