<?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, 18 May 2013 09:33:08 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Debuggable Blog: Supressing Errors in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/11848</guid>
      <link>http://www.phpdeveloper.org/news/11848</link>
      <description><![CDATA[<p>
<i>Felix Geisendorfer</i> has posted two new items to the Debuggable blog looking at suppressing errors in your applications - and no, that doesn't mean <a href="http://www.phpdeveloper.org/news/11672">using the @ operator</a> either.
</p>
<blockquote>
As of late I am getting sick of some best practices I have taught myself. Never using the @-error suppressing operator quickly moving to the top of the list. Before you start crying out loud (I know you will), let me say this: I do not mean to encourage anybody to use the @-operator. Applying the practice herein introduced may result in permanent damage to your coding habits and could serve as a gateway behavior to writing shitty code.
</blockquote>
<p>
He gives an example in the <a href="http://debuggable.com/posts/suppressing-php-errors-for-fun-and-profit">first post</a> of a place where he failed to properly check to ensure an element existed before checking a element of it. The <a href="http://debuggable.com/posts/suppressing-suppressing-php-errors-with-emptiness">second post</a> provides an interesting solution to the same problem - using <a href="http://php.net/empty">empty</a> on the element/subelement to check its existence.
</p>]]></description>
      <pubDate>Fri, 30 Jan 2009 11:14:58 -0600</pubDate>
    </item>
  </channel>
</rss>
