<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tinsology &#187; Errors</title>
	<atom:link href="http://tinsology.net/tag/errors/feed/" rel="self" type="application/rss+xml" />
	<link>http://tinsology.net</link>
	<description>Read Me</description>
	<lastBuildDate>Thu, 20 May 2010 02:41:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>PHP Error Handling</title>
		<link>http://tinsology.net/2009/04/php-error-handling/</link>
		<comments>http://tinsology.net/2009/04/php-error-handling/#comments</comments>
		<pubDate>Mon, 20 Apr 2009 18:47:56 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Errors]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=395</guid>
		<description><![CDATA[Previously I wrote about <a href="http://tinsology.net/2009/04/php-exception-handling/" title="PHP Exceptions">Exceptions as a way of dealing with error cases in PHP</a>. Exceptions are a great way to anticipate errors and handle them appropriately. Unfortunately, however, it is not possible to anticipate every error and you users still might be presented with an ugly error message generated by PHP. One way to prevent users from seeing warnings or errors generated by PHP is to turn off error reporting. The down side to using this method is that you might not be aware that an error is occuring, and you'll be even less aware of <a href="http://tinsology.net/2009/04/php-error-handling/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/04/php-exception-handling/' rel='bookmark' title='Permanent Link: PHP Exception Handling'>PHP Exception Handling</a></li>
<li><a href='http://tinsology.net/2009/03/consolidating-error-pages-with-htaccess/' rel='bookmark' title='Permanent Link: Consolidating Error Pages with .htaccess'>Consolidating Error Pages with .htaccess</a></li>
<li><a href='http://tinsology.net/2010/04/php-polymorphism/' rel='bookmark' title='Permanent Link: PHP Overloading'>PHP Overloading</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/04/php-error-handling/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>PHP Exception Handling</title>
		<link>http://tinsology.net/2009/04/php-exception-handling/</link>
		<comments>http://tinsology.net/2009/04/php-exception-handling/#comments</comments>
		<pubDate>Sat, 11 Apr 2009 05:05:22 +0000</pubDate>
		<dc:creator>Tinsley</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Errors]]></category>
		<category><![CDATA[Exceptions]]></category>

		<guid isPermaLink="false">http://tinsology.net/?p=396</guid>
		<description><![CDATA[If you've ever coded in Java or C++ you probably know what exceptions are. If not, that's okay. I'll go over the basics. 
 
Exceptions modify the control flow of a program. Usually, they are generated by functions when an error occurs. Throwing and catching exceptions allow the programmer to anticipate an error and handle it accordingly. For example: Say you write a function to open up a file and read its contents. When the function tries to open the file, however, it finds that the file does not exist. Generally this would just generate a nasty error and your <a href="http://tinsology.net/2009/04/php-exception-handling/">Read More</a>

Related posts:<ol><li><a href='http://tinsology.net/2009/04/php-error-handling/' rel='bookmark' title='Permanent Link: PHP Error Handling'>PHP Error Handling</a></li>
</ol>]]></description>
		<wfw:commentRss>http://tinsology.net/2009/04/php-exception-handling/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
