<?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 18:47:45 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Dikini.net: Rewriting macros - the peculiar case of php]]></title>
      <guid>http://www.phpdeveloper.org/news/6062</guid>
      <link>http://www.phpdeveloper.org/news/6062</link>
      <description><![CDATA[<p>
On Dikiki.net today, there's <a href="http://dikini.net/16.08.2006/rewriting_macros_the_peculiar_case_of_php">a new post</a> that's a continuation of a series (<a href="http://www.phpdeveloper.org/news/5882">first post</a>, <a href="http://www.phpdeveloper.org/news/5923">second post</a>) dealing with macro programming in PHP.
</p>
<blockquote>
Without going into theoretical details, some of which are quite alien to me, I'll try to describe some of the challenges that pattern patching rewriting macros might pose for a language like php. After brief explanation what kind of a beast is this, I try to explore some of the finer points, which might cause problems. The intent of this post is to sketch a design and highlight some of the possible issues.
</blockquote>
<p>
He <a href="http://dikini.net/16.08.2006/rewriting_macros_the_peculiar_case_of_php">breaks up the post</a> into a few sections:
<ul>
<li>pattern matching rewrite only macros - a bird eye view
<li>Transformation time
<li>Basic/skeleton shapes and intermediate shapes
<li>Code generation issues specific to php
<li>Hygiene
<li>A rough macro shape outline
<li>Output/Status of the project
</ul>
There are code examples (of how it should work) and explainations of the issues PHP would face to accomplish this goal.
</p>]]></description>
      <pubDate>Thu, 17 Aug 2006 07:29:04 -0500</pubDate>
    </item>
  </channel>
</rss>
