<?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>Tue, 21 May 2013 01:55:25 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lukas Smith's Blog: Brideing the rift between PEAR_Error and PEAR_Exception]]></title>
      <guid>http://www.phpdeveloper.org/news/5608</guid>
      <link>http://www.phpdeveloper.org/news/5608</link>
      <description><![CDATA[<p>
<i>Lukas Smith</i> has a <a href="http://pooteeweet.org/blog/430">quick post</a> today about some of the tension that's come up between to PEAR error handling packages and something he's created to try to help calm things down.
</p>
<blockquote>
Well there is a lot of back and forth about if PEAR should mandate PEAR_Error or PEAR_Exceptions or neither for new packages. This also relates to the question of PHP5 E_STRICT compliance which PEAR_Error obviously is not.
</blockquote>
<p>
His quick fix for the problem? <a href="http://pooteeweet.org/pear/error_proxy.phps">Two proxy classes</a> that would make switching between either of the two error handling classes as simple as changing out which proxy you're using.
</p>]]></description>
      <pubDate>Fri, 16 Jun 2006 09:07:11 -0500</pubDate>
    </item>
  </channel>
</rss>
