<?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: Guido On Django In 2006</title>
	<atom:link href="http://blog.gordaen.com/2008/04/03/guido-on-django-in-2006/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gordaen.com/2008/04/03/guido-on-django-in-2006/</link>
	<description>Ramblings about art, education, culture and a lot more</description>
	<lastBuildDate>Fri, 12 Mar 2010 08:07:09 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ian Clifton</title>
		<link>http://blog.gordaen.com/2008/04/03/guido-on-django-in-2006/comment-page-1/#comment-79542</link>
		<dc:creator>Ian Clifton</dc:creator>
		<pubDate>Sat, 05 Apr 2008 22:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gordaen.com/?p=413#comment-79542</guid>
		<description>Error reporting should always be configurable.  On a live server, you don&#039;t want the end user to see any errors they don&#039;t have to, and you want to catch the drastic ones to give a more friendly message.  On a development server, you want all errors (no matter how small) to show up, so you can code using best practices.

A developer shouldn&#039;t have to consider the error level when building an app, because it should be built to have no notices and to properly handle any other problems.

I like that you can specify your own error handler in PHP, that way you can throw exceptions if you want or log/email error information, etc.</description>
		<content:encoded><![CDATA[<p>Error reporting should always be configurable.  On a live server, you don&#8217;t want the end user to see any errors they don&#8217;t have to, and you want to catch the drastic ones to give a more friendly message.  On a development server, you want all errors (no matter how small) to show up, so you can code using best practices.</p>
<p>A developer shouldn&#8217;t have to consider the error level when building an app, because it should be built to have no notices and to properly handle any other problems.</p>
<p>I like that you can specify your own error handler in PHP, that way you can throw exceptions if you want or log/email error information, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vitaliy</title>
		<link>http://blog.gordaen.com/2008/04/03/guido-on-django-in-2006/comment-page-1/#comment-79535</link>
		<dc:creator>Vitaliy</dc:creator>
		<pubDate>Sat, 05 Apr 2008 21:38:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gordaen.com/?p=413#comment-79535</guid>
		<description>&gt; change the error reporting level in PHP and even log the notices
IMO php did very big mistake when they allow to configure error reporting level and their quote system... 
If error reporting will be configurable - then every developer will need to make some checks and more lines of code if he wants to make his app more portable.
There should be only build-in &#039;on&#039; or &#039;off&#039; templates error reporting - but not configurable!</description>
		<content:encoded><![CDATA[<p>&gt; change the error reporting level in PHP and even log the notices<br />
IMO php did very big mistake when they allow to configure error reporting level and their quote system&#8230;<br />
If error reporting will be configurable &#8211; then every developer will need to make some checks and more lines of code if he wants to make his app more portable.<br />
There should be only build-in &#8216;on&#8217; or &#8216;off&#8217; templates error reporting &#8211; but not configurable!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
