<?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 02:37:20 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[McGlockenshire.com: Waiting for PHP 5.4: Death to prehistoric cruft]]></title>
      <guid>http://www.phpdeveloper.org/news/16659</guid>
      <link>http://www.phpdeveloper.org/news/16659</link>
      <description><![CDATA[<p>
On McGlockenshire.com there's a recent post looking at some of the <a href="http://mcglockenshire.com/blog/posts/waiting-for-php-5-4-death-to-prehistoric-cruft.html">features of the upcoming PHP 5.4 release</a> and how they'll be glad to get rid of the "prehistoric cruft" that's accumulated around the language over the years.
</p>
<blockquote>
It's incredibly rare for the Internals crew to ever consider breaking backwards compatibility, but some of the most important changes in PHP 5.4 do just that by removing old "features." None of these changes should impact modern PHP code. If somehow you get bitten by any of these changes, chances are that your code dates from the PHP 4 era.
</blockquote>
<p>
Included in his list of updates/removals/improvements are things like the full removal of safe_mode, dropping register_globals, pulling out call time pass by reference and the removal of the session registration methods.
</p>]]></description>
      <pubDate>Mon, 01 Aug 2011 10:20:04 -0500</pubDate>
    </item>
  </channel>
</rss>
