<?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>Sat, 22 Nov 2008 01:59:13 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Matthew Weier O'Phinney's Blog: Migrating OOP Libraries and Frameworks to PHP 5.3]]></title>
      <guid>http://www.phpdeveloper.org/news/10529</guid>
      <link>http://www.phpdeveloper.org/news/10529</link>
      <description><![CDATA[<p>
<i>Matthew Weier O'Phinney</i> recently <a href="http://weierophinney.net/matthew/archives/181-Migrating-OOP-Libraries-and-Frameworks-to-PHP-5.3.html">posted about</a> a method he's come up with for migrating your object-oriented libraries (including frameworks) over to the upcoming PHP 5.3 version of the language.
</p>
<blockquote>
With PHP 5.3 coming up on the horizon, I'm of course looking forward to using namespaces. 
</blockquote>
<p>
He gives an example of how useful these namespaces can be for you and your code, but points out one failing point - trying to define classes in a namespace that are named the same as a built-in keyword for PHP. There's already been a suggestion to add a captial "I" in front of the class name to prevent this collision.
</p>
<p>
There's also the problem of throwing custom exceptions - unless you use the namespace properly your script will just throw a default exception.
</p>]]></description>
      <pubDate>Wed, 02 Jul 2008 10:24:02 -0500</pubDate>
    </item>
  </channel>
</rss>
