<?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 20:46:58 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHP 10.0 Blog: More inlining]]></title>
      <guid>http://www.phpdeveloper.org/news/6734</guid>
      <link>http://www.phpdeveloper.org/news/6734</link>
      <description><![CDATA[<p>
On the PHP 10.0 Blog, <i>Stas</i> <a href="http://php100.wordpress.com/2006/11/13/more-inlining/">talks more about</a> inlining in PHP functions - some of the bad things this time (see <a href="http://php100.wordpress.com/2006/10/16/inline-evals/">here</a> and <a href="http://php100.wordpress.com/2006/10/26/faster-better-assert/">here</a> for other comments), including things that could break an application if not handled correctly.
</p>
<blockquote>
Performance benefits from inlining simple functions might be significant, since function call in PHP is not cheap. We'd have some potential problems there.
</blockquote>
<p>
Included in the list are things like:
<ul>
<li>Variable scoping - we don't want function variables to mess with our scope, so we'd probably rename them or something.
<li>Then we might get a problem if function messing with current scope is called indirectly so we can't really know. 
<li>And then some may use end-of-scope for destruction of variables that have dtors, so when we'd clean up these variables?
</ul>
</p>]]></description>
      <pubDate>Mon, 20 Nov 2006 08:10:00 -0600</pubDate>
    </item>
  </channel>
</rss>
