<?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>Sat, 25 May 2013 01:07:37 -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>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: AspectPHP]]></title>
      <guid>http://www.phpdeveloper.org/news/5010</guid>
      <link>http://www.phpdeveloper.org/news/5010</link>
      <description><![CDATA[As was mentioned in <a href="http://www.phpdeveloper.org/news/4833">one of his previous blog posts</a>, <i>Sebastian Bergmann</i> has been working up his own PHP version of an aspect-oriented framework. According to <a href="http://www.sebastian-bergmann.de/blog/archives/589-AspectPHP.html">this new post</a>, he's already done some work on <a href="http://www.sebastian-bergmann.de/AspectPHP/">the project</a> and has created a page with more information.
<p>
<quote>
<i>
As I wrote earlier, I am not satisfied with the <a href="http://www.sebastian-bergmann.de/blog/archives/573-Current-State-of-AOP-for-PHP.html">Current State of AOP for PHP</a> and started to work on <a href="http://www.sebastian-bergmann.de/AspectPHP/">AspectPHP</a> a while ago. Today I am going to share my ideas on the subject.
<p>
What sets AspectPHP apart from other implementations of <a href="http://en.wikipedia.org/wiki/Aspect-oriented_programming">Aspect-Oriented Programming</a> is its simplicity: aspects are plain PHP classes that declare <a href="http://en.wikipedia.org/wiki/Pointcut">pointcuts</a> using <a href="http://en.wikipedia.org/wiki/Annotation">annotations</a>.
</i>
</quote>
<p>
He <a href="http://www.sebastian-bergmann.de/blog/archives/589-AspectPHP.html">gives an example</a> of this kind of functionality, including a bit of code to illustrate. The example logs all method calls and, in this case, simply outputs them to the browser.
<p>
Unfortunately, he also mentions that, at this time, he doesn't have any code for the framework that he can release, but you can check out <a href="http://www.sebastian-bergmann.de/AspectPHP/">the site he's created</a> for more information.]]></description>
      <pubDate>Mon, 20 Mar 2006 06:54:17 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Current State of AOP for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/4833</guid>
      <link>http://www.phpdeveloper.org/news/4833</link>
      <description><![CDATA[<i>Sebastian Bergmann</i> has posted a <a href="http://www.sebastian-bergmann.de/blog/archives/573-Current-State-of-AOP-for-PHP.html">current state of AOP for PHP</a> summary on his blog today, a look at a few resources and an addition of one of his own.
<p>
<quote>
<i>
I know about four existing approaches to faciliate Aspect-Oriented Programming with the PHP Programming Language:
<ul>
<li><a href="http://www.phpaspect.org/">PHPAspect</a>
<li><a href="http://www.aophp.net/">Aspect-oriented PHP</a>
<li><a href="http://www.cs.toronto.edu/~yijun/aspectPHP/">aspectPHP</a>
<li><a href="http://pear.php.net/pepr/pepr-proposal-show.php?id=315">AOP Library for PHP</a>
</ul>
</i>
</quote>
<p>
But, as was previously mentioned, he's not happy with the current implementations, so he's <a href="http://www.sebastian-bergmann.de/blog/archives/573-Current-State-of-AOP-for-PHP.html">working up his own</a> - AspectPHP...]]></description>
      <pubDate>Mon, 13 Feb 2006 07:18:24 -0600</pubDate>
    </item>
  </channel>
</rss>
