<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Mayday, Mayday, Mayday - PHP Going Down</title>
	<atom:link href="http://www.eggplant.ws/blog/php/mayday-php-going-down/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/</link>
	<description>Ramblings of a web developer</description>
	<pubDate>Mon, 06 Feb 2012 23:56:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: beakt</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-237</link>
		<dc:creator>beakt</dc:creator>
		<pubDate>Sat, 28 Aug 2010 08:14:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-237</guid>
		<description>This is a terrific article. Not the usual regurgitating of the PHP manual that you usually find when you Google for new knowledge about PHP.  This article is unique and clever.  Very useful, Michael.

I implemented this on my system tonight.  Now, when I forget a semi-colon or screw up my brackets, I can have my web server (by checking $_SERVER['remote_addr']) display the error only for me, and display a friendly apology to my users.  I don't have to go to my Putty window and run 'tail phperror.log' any more!

I can add this: As you may have noticed, this method won't catch a parse error if the definition/registration of the shutdown function is in the same file. But, if you put the definition/registration of the shutdown function into an auto_prepend_file, then it will catch a parse error in your main PHP file called via the URI.</description>
		<content:encoded><![CDATA[<p>This is a terrific article. Not the usual regurgitating of the PHP manual that you usually find when you Google for new knowledge about PHP.  This article is unique and clever.  Very useful, Michael.</p>
<p>I implemented this on my system tonight.  Now, when I forget a semi-colon or screw up my brackets, I can have my web server (by checking $_SERVER['remote_addr']) display the error only for me, and display a friendly apology to my users.  I don&#8217;t have to go to my Putty window and run &#8216;tail phperror.log&#8217; any more!</p>
<p>I can add this: As you may have noticed, this method won&#8217;t catch a parse error if the definition/registration of the shutdown function is in the same file. But, if you put the definition/registration of the shutdown function into an auto_prepend_file, then it will catch a parse error in your main PHP file called via the URI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andi zaugg</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-233</link>
		<dc:creator>andi zaugg</dc:creator>
		<pubDate>Tue, 11 May 2010 12:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-233</guid>
		<description>cool!
thank you very much!</description>
		<content:encoded><![CDATA[<p>cool!<br />
thank you very much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian S.</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-225</link>
		<dc:creator>Christian S.</dc:creator>
		<pubDate>Tue, 15 Dec 2009 11:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-225</guid>
		<description>Hey, I am happy about this blog entry. I searched for a solution to catch fatal errors and with Your help I could solve my problem :-)
Thank You very much!</description>
		<content:encoded><![CDATA[<p>Hey, I am happy about this blog entry. I searched for a solution to catch fatal errors and with Your help I could solve my problem <img src='http://www.eggplant.ws/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /><br />
Thank You very much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claude</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-221</link>
		<dc:creator>Claude</dc:creator>
		<pubDate>Thu, 22 Oct 2009 18:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-221</guid>
		<description>Please change the title of your article to something more search engine friendly. Something like this would be much better:

PhP Fatal Error Handling</description>
		<content:encoded><![CDATA[<p>Please change the title of your article to something more search engine friendly. Something like this would be much better:</p>
<p>PhP Fatal Error Handling</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rob</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-215</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Sun, 10 May 2009 15:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-215</guid>
		<description>I would not have thought that register_shutdown_function could catch E_PARSE, when even set_error_handler cannot. This is great, thanks!</description>
		<content:encoded><![CDATA[<p>I would not have thought that register_shutdown_function could catch E_PARSE, when even set_error_handler cannot. This is great, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Wood</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-13</link>
		<dc:creator>Martin Wood</dc:creator>
		<pubDate>Wed, 03 Sep 2008 10:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-13</guid>
		<description>Thanks, Michael.

That was exactly what I was looking for to deal with a problem I have dealing with potentially invalid PHP files that are generated from user input.</description>
		<content:encoded><![CDATA[<p>Thanks, Michael.</p>
<p>That was exactly what I was looking for to deal with a problem I have dealing with potentially invalid PHP files that are generated from user input.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fehlerbehandlung in PHP &#124; Mirko Bald</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-6</link>
		<dc:creator>Fehlerbehandlung in PHP &#124; Mirko Bald</dc:creator>
		<pubDate>Mon, 25 Aug 2008 20:28:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-6</guid>
		<description>[...] http://www.eggplant.ws/blog/php/mayday-php-going-down/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.eggplant.ws/blog/php/mayday-php-going-down/" rel="nofollow">http://www.eggplant.ws/blog/php/mayday-php-going-down/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web 2.0 Announcer</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-5</link>
		<dc:creator>Web 2.0 Announcer</dc:creator>
		<pubDate>Mon, 25 Aug 2008 09:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-5</guid>
		<description>&lt;strong&gt;Mayday, Mayday, Mayday - PHP Going Down...&lt;/strong&gt;

[...]PHP provides a variety of tools for handling errors. However, there is a range of fatal errors that PHP does not directly provide tools for you to handle them.[...]...</description>
		<content:encoded><![CDATA[<p><strong>Mayday, Mayday, Mayday - PHP Going Down&#8230;</strong></p>
<p>[...]PHP provides a variety of tools for handling errors. However, there is a range of fatal errors that PHP does not directly provide tools for you to handle them.[...]&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hodicska Gergely</title>
		<link>http://www.eggplant.ws/blog/php/mayday-php-going-down/comment-page-1/#comment-4</link>
		<dc:creator>Hodicska Gergely</dc:creator>
		<pubDate>Mon, 25 Aug 2008 06:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.eggplant.ws/blog/?p=28#comment-4</guid>
		<description>Great article! A little addition: output handlers will be called on fatal errors too.</description>
		<content:encoded><![CDATA[<p>Great article! A little addition: output handlers will be called on fatal errors too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

