<?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, 15 May 2008 23:06:28 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Stubbles Blog: Traits for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/9669</guid>
      <link>http://www.phpdeveloper.org/news/9669</link>
      <description><![CDATA[<p>
On the Stubbles blog, <i>Frank Kleine</i> has <a href="http://www.stubbles.org/archives/42-Traits-for-PHP.html">pointed out</a> a <a href="http://news.php.net/php.internals/35562">proposal</a> from <i>Stefan Marr</i> to include functionality for traits in PHP.
</p>
<blockquote>
As a language construct within PHP it would be very easy to do the same, but easier to learn and to use. Beside some keyword issues (the RFC uses "use" as keyword, but this will of course conflict with <a href="http://php.net/manual/en/language.namespaces.using.php">namespaces</a>) I'm wondering what this will have an impact on reflection - the RFC stays unclear about this. 
</blockquote>
<p>
A trait is a free-floating chink of functionality that, instead of being confined to a class (or file) that has to be called on to use it, exists where the developer can use it from anywhere at any time. This helps solve some of the issues with single inheritance in PHP.
</p>]]></description>
      <pubDate>Wed, 20 Feb 2008 11:17:00 -0600</pubDate>
    </item>
  </channel>
</rss>
