<?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 20:22:49 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Northclick Blog: Getting the PHP fatal errors]]></title>
      <guid>http://www.phpdeveloper.org/news/7843</guid>
      <link>http://www.phpdeveloper.org/news/7843</link>
      <description><![CDATA[<p>
From the Nothclick dev blog, there's <a href="http://blog.northclick.de/archives/17">this new post</a> from <i> Soenke Ruempler</i> that talks about working with error messages in PHP, specifically with fatal errors.
</p>
<blockquote>
One big issue of the PHP error handling is that there's no built-in way to catch fatal errors with an user-defined error handler. So I thought a little bit about it and maybe you have better approaches or solutions...
</blockquote>
<p>
With the goal of emailing the developers when such an error is thrown, he comes up with three different "storage methods" - using syslog, sapi, or a common logfile - and two different methods for watching them - file watching and syslogger. He works through these two options, trying to figure out which out be the simplest to implement.
</p>
<p>
He comes to the conclusion, though, that he might just be better off with one of the packages already out there to do something similar. Of the four he found, <a href="http://sourceforge.net/projects/swatch/">Swatch</a> seemed to fit the best. He includes configuration and setup info to illustrate.
</p>]]></description>
      <pubDate>Tue, 15 May 2007 07:49:00 -0500</pubDate>
    </item>
  </channel>
</rss>
