<?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, 19 Jun 2013 14:58:15 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Jacob Santos's Blog: Don't Advocate Inner Classes]]></title>
      <guid>http://www.phpdeveloper.org/news/6009</guid>
      <link>http://www.phpdeveloper.org/news/6009</link>
      <description><![CDATA[<p>
<I>Jacob Santos</i> talks in <a href="http://www.santosj.name/php/dont-advocate-subclasses/">this new blog post</a> about something that, if added to PHP, just might be more trouble than it's worth - inner classes.
</p>
<blockquote>
<p>
Inner Classes are contained in parent classes and offer a sort of namespace mechanism for the public and open private class data transfer for private subclasses.
</p>
<p>
The functionality is already available in other languages, but the question is whether it is needed in PHP. The short answer is no. With PHP execution model, it would further slow down and bloat PHP compilation.
</p>
</blockquote>
<p>
He <a href="http://www.santosj.name/php/dont-advocate-subclasses/">demonstrates their purpose</a> with some simple examples but also gives the reasons why it would be a bad thing to try to include them, including the better choice of namespaces over inner classes.
</p>]]></description>
      <pubDate>Fri, 11 Aug 2006 07:38:43 -0500</pubDate>
    </item>
  </channel>
</rss>
