<?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: PHP error handling</title>
	<atom:link href="http://www.puremango.co.uk/2009/07/php-error-handling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.puremango.co.uk/2009/07/php-error-handling/</link>
	<description>innovative coding, tutorials, web stuff.</description>
	<lastBuildDate>Mon, 22 Mar 2010 09:06:29 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: PHP error handling « puremango.co.uk &#124; Errors &#38; Geeks</title>
		<link>http://www.puremango.co.uk/2009/07/php-error-handling/comment-page-1/#comment-1489</link>
		<dc:creator>PHP error handling « puremango.co.uk &#124; Errors &#38; Geeks</dc:creator>
		<pubDate>Tue, 07 Jul 2009 11:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.puremango.co.uk/?p=548#comment-1489</guid>
		<description>[...] more here:  PHP error handling « puremango.co.uk Tags: code, entry, [...]</description>
		<content:encoded><![CDATA[<p>[...] more here:  PHP error handling « puremango.co.uk Tags: code, entry, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: user24</title>
		<link>http://www.puremango.co.uk/2009/07/php-error-handling/comment-page-1/#comment-1443</link>
		<dc:creator>user24</dc:creator>
		<pubDate>Sun, 05 Jul 2009 16:30:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.puremango.co.uk/?p=548#comment-1443</guid>
		<description>cheers ;0) Yeah I did write a little thing to make debug_backtrace prettier at one point too, so you effectively step through the whole execution path and dump out the function, file and line number etc. But I found this more useful in general.</description>
		<content:encoded><![CDATA[<p>cheers ;0) Yeah I did write a little thing to make debug_backtrace prettier at one point too, so you effectively step through the whole execution path and dump out the function, file and line number etc. But I found this more useful in general.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Del</title>
		<link>http://www.puremango.co.uk/2009/07/php-error-handling/comment-page-1/#comment-1438</link>
		<dc:creator>Del</dc:creator>
		<pubDate>Sun, 05 Jul 2009 12:31:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.puremango.co.uk/?p=548#comment-1438</guid>
		<description>Yeah, i have used this method before by calling the debug_backtrace() function, my implementation wasn&#039;t as clean as yours but it essentially did the same thing.

Very useful and a great article ... Keep them coming!</description>
		<content:encoded><![CDATA[<p>Yeah, i have used this method before by calling the debug_backtrace() function, my implementation wasn&#8217;t as clean as yours but it essentially did the same thing.</p>
<p>Very useful and a great article &#8230; Keep them coming!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
