<?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>Sun, 07 Sep 2008 09:28:59 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Eirik Hoem's Blog: Dying with grace - PHP's register_shutdown_function]]></title>
      <guid>http://www.phpdeveloper.org/news/9808</guid>
      <link>http://www.phpdeveloper.org/news/9808</link>
      <description><![CDATA[<p>
<i>Eirik Hoem</i> has <a href="http://eirikhoem.wordpress.com/2008/03/15/dying-with-grace-phps-register_shutdown_function/">posted a new look</a> at a function that can be amazingly helpful when you have a script with issues that needs a little extra help cleaning up after itself - <a href="http://no2.php.net/register_shutdown_function">register_shutdown_function</a>.
</p>
<blockquote>
Scripts tend to die, and that's not usually nice. We do not want to show the user a fatal error nor a blank page (display errors off) . PHP has a function called <a href="http://no2.php.net/register_shutdown_function">register_shutdown_function</a> which lets us set up a function which is called at execution shutdown. What this means is that our function will be executed when our script is done executing / dying and PHP execution is about to shut down.
</blockquote>
<p>
He <a href="http://eirikhoem.wordpress.com/2008/03/15/dying-with-grace-phps-register_shutdown_function/">suggests</a> various things that can be done with the functionality, including checking for successful script execution (via a false variable that can be checked for success).
</p>]]></description>
      <pubDate>Mon, 17 Mar 2008 12:02:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Error Handling in PHP - Coding Defensively]]></title>
      <guid>http://www.phpdeveloper.org/news/4649</guid>
      <link>http://www.phpdeveloper.org/news/4649</link>
      <description><![CDATA[DevShed has <a href="http://www.devshed.com/c/a/PHP/Error-Handling-in-PHP-Coding-Defensively/">a new article</a> posted today dealing with error reporting in PHP applications.
<p>
<quote>
<i>
Since error handling is something that you should introduce (at least progressively) into your applications, in this article I'll explore some of the most common error checking methods available in PHP, in order to make web applications much more robust and reliable. 
<p>
The end result of this experience will be an illustrative list of hands-on examples that utilize different error handling methods, ranging in from using simple "die()" statements, to manipulating errors within an object-oriented context, by utilizing exceptions.
</i>
</quote>
<p>
They <a href="http://www.devshed.com/c/a/PHP/Error-Handling-in-PHP-Coding-Defensively/">cover</a> things like the basic die() statement, triggering errors in your code with the trigger_error() function, using the error handling in PEAR, and setting boolean flags to catch when things go wrong...]]></description>
      <pubDate>Thu, 12 Jan 2006 06:34:19 -0600</pubDate>
    </item>
  </channel>
</rss>
