<?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>Wed, 22 May 2013 01:34:42 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Larry Garfield's Blog: Drupal 7 gets introspective code registry]]></title>
      <guid>http://www.phpdeveloper.org/news/10143</guid>
      <link>http://www.phpdeveloper.org/news/10143</link>
      <description><![CDATA[<p>
<i>Larry Garfield</i> talks about a new feature of Drupal 7 in <a href="http://www.garfieldtech.com/drupal-7-registry">a new post</a> to his blog - the new introspective code registry that's been introduced in this latest version.
</p>
<blockquote>
As a GHOP Task , Cornil did a performance analysis of Drupal and found its two largest performance drains were the bootstrap process and the theming layer. Quite simply, Drupal spends too much time including code. [...] Fortunately, Drupal 7's self-learning <a href="http://drupal.org/node/221964">code registry system</a> has <a href="http://drupal.org/cvs?commit=114916">just</a> <a href="http://drupal.org/cvs?commit=114932">landed</a>, which should obliterate most of the wasted bootstrap cost.
</blockquote>
<p>
<i>Larry</i> <a href="http://www.garfieldtech.com/drupal-7-registry">describes</a> the "heart of it all", the token_get_all call, that parses through an entire PHP file, splitting out things like classes included and functions called. This is passed through a function_exists call to the current script and, if it's already there, the file isn't included repetitively.
</p>]]></description>
      <pubDate>Thu, 08 May 2008 12:53:14 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[SitePoint PHP Blog: Index of PHP tokens for Emacs and beyond]]></title>
      <guid>http://www.phpdeveloper.org/news/9074</guid>
      <link>http://www.phpdeveloper.org/news/9074</link>
      <description><![CDATA[<p>
<i>Troels Knak-Nielsen</i> has <a href="http://www.sitepoint.com/blogs/2007/11/18/index-of-php-tokens-for-emacs-and-beyond/">posted a script</a> that he's developed (for use in Emacs) to look through a PHP file and pull out all of the classes and functions found inside.
</p>
<blockquote>
As you probably know, PHP has a ridiculous amount of functions for all kinds of things, and as it happens, <a href="http://docs.php.net/manual/en/function.token-get-all.php">token_get_all</a> gives access to the Zend Engine tokenizer. In other words, the same chunk of code, which PHP itself uses, when reading a .php file. This provides an excellent base for writing a script, which can parse the socks off <a href="http://ctags.sourceforge.net/">ctags</a>.
</blockquote>
<p>
The emacs file to bind the editor and the PHP script together is also included, making it as simple to use as binding the function key of your choice to the "php-tokens" script.
</p>]]></description>
      <pubDate>Mon, 19 Nov 2007 14:38:00 -0600</pubDate>
    </item>
  </channel>
</rss>
