<?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: 5 Tips for Coding Cleaner PHP</title>
	<atom:link href="http://www.fullondesign.co.uk/coding/php/616-5-tips-for-coding-cleaner-php.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.fullondesign.co.uk/coding/php/616-5-tips-for-coding-cleaner-php.htm</link>
	<description>Design &#38; Web Technologies</description>
	<lastBuildDate>Sat, 31 Jul 2010 10:22:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Must Read PHP Articles and Resources &#171; UR-Technology</title>
		<link>http://www.fullondesign.co.uk/coding/php/616-5-tips-for-coding-cleaner-php.htm/comment-page-1#comment-2536</link>
		<dc:creator>Must Read PHP Articles and Resources &#171; UR-Technology</dc:creator>
		<pubDate>Sun, 07 Mar 2010 02:32:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.fullondesign.co.uk/?p=616#comment-2536</guid>
		<description>[...] 5 Tips for Coding Cleaner PHP [...]</description>
		<content:encoded><![CDATA[<p>[...] 5 Tips for Coding Cleaner PHP [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 45 Must Read PHP Articles and Resources</title>
		<link>http://www.fullondesign.co.uk/coding/php/616-5-tips-for-coding-cleaner-php.htm/comment-page-1#comment-2424</link>
		<dc:creator>45 Must Read PHP Articles and Resources</dc:creator>
		<pubDate>Fri, 08 Jan 2010 17:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.fullondesign.co.uk/?p=616#comment-2424</guid>
		<description>[...] 5 Tips for Coding Cleaner PHP [...]</description>
		<content:encoded><![CDATA[<p>[...] 5 Tips for Coding Cleaner PHP [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Super Star &#187; Blog Archive &#187; PHP Articles and Resources for all levels</title>
		<link>http://www.fullondesign.co.uk/coding/php/616-5-tips-for-coding-cleaner-php.htm/comment-page-1#comment-1461</link>
		<dc:creator>Web Super Star &#187; Blog Archive &#187; PHP Articles and Resources for all levels</dc:creator>
		<pubDate>Tue, 23 Jun 2009 06:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.fullondesign.co.uk/?p=616#comment-1461</guid>
		<description>[...] 5 Tips for Coding Cleaner PHP [...]</description>
		<content:encoded><![CDATA[<p>[...] 5 Tips for Coding Cleaner PHP [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.fullondesign.co.uk/coding/php/616-5-tips-for-coding-cleaner-php.htm/comment-page-1#comment-1381</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Sat, 20 Jun 2009 23:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.fullondesign.co.uk/?p=616#comment-1381</guid>
		<description>Sorry but half of this is bad advice...

Whitespace: you example doesn&#039;t go far enough. how about some extra line breaks, and spaces around braces and &#039;while&#039;, etc. I refuse to believe anyone writes code like you &quot;Bad&quot; example.

Never Delete: no, no, no. Never leave commented code in your files, it just clutters up otherwise readable functions. It&#039;s fine to comment stuff while testing, it obviously saves time when switching between different logic, but once everything&#039;s working the code should be neat!

Use braces: well this is a controversial one. Firstly your modified &#039;if&#039; statement is as fugly, if not moreso. If there is only one statement for the &#039;if&#039; or &#039;while&#039; there&#039;s no reason to use braces, just put the statement n the next line. It&#039;s blindingly obvious that if you add another statement to the &#039;if&#039; you&#039;ll need to use braces.</description>
		<content:encoded><![CDATA[<p>Sorry but half of this is bad advice&#8230;</p>
<p>Whitespace: you example doesn&#8217;t go far enough. how about some extra line breaks, and spaces around braces and &#8216;while&#8217;, etc. I refuse to believe anyone writes code like you &#8220;Bad&#8221; example.</p>
<p>Never Delete: no, no, no. Never leave commented code in your files, it just clutters up otherwise readable functions. It&#8217;s fine to comment stuff while testing, it obviously saves time when switching between different logic, but once everything&#8217;s working the code should be neat!</p>
<p>Use braces: well this is a controversial one. Firstly your modified &#8216;if&#8217; statement is as fugly, if not moreso. If there is only one statement for the &#8216;if&#8217; or &#8216;while&#8217; there&#8217;s no reason to use braces, just put the statement n the next line. It&#8217;s blindingly obvious that if you add another statement to the &#8216;if&#8217; you&#8217;ll need to use braces.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
