<?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 11:47:18 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHP 10.0 Blog: Kill resources]]></title>
      <guid>http://www.phpdeveloper.org/news/7858</guid>
      <link>http://www.phpdeveloper.org/news/7858</link>
      <description><![CDATA[<p>
In a <a href="http://php100.wordpress.com/2007/05/16/kill-resources/">new post</a> to the PHP 10.0 blog today, <i>Stas</i> asks the question "Why do we still have resource type in PHP?"
</p>
<blockquote>
Since 5.x, objects are perfectly capable on encapsulating any void * transparently (there's at least 2 Java bridges doing that, for example) and of course using objects doesn't force you to use OO syntax. [...] So objects as I see it can do anything resources can do. And much more - you could extend it (had we had file as object and not resource, streams probably would be much easier to implement), serialize it (provided correct methods of course), etc., etc.
</blockquote>
<p>
He <a href="http://php100.wordpress.com/2007/05/16/kill-resources/">suggests letting them go</a> all together and letting objects swoop in and take over, making things simpler to manage.
</p>]]></description>
      <pubDate>Thu, 17 May 2007 07:56:00 -0500</pubDate>
    </item>
  </channel>
</rss>
