<?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 for Neverending Nexua</title>
	<atom:link href="http://blog.nexua.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nexua.org</link>
	<description>Programmer with a bad sleep schedule.</description>
	<lastBuildDate>Wed, 18 Jan 2012 12:21:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on PHP Coding Conventions by Anonymous</title>
		<link>http://blog.nexua.org/php-coding-conventions/#comment-1620</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 18 Jan 2012 12:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nexua.org/?p=629#comment-1620</guid>
		<description>It states on Tip #4 that it should only be done in single line instances.

So Tip #4 has cured your issue of attempting multiple lines on something that is &lt;b&gt;solely&lt;/b&gt; for single line conditions. It&#039;s in the language for a reason ;)</description>
		<content:encoded><![CDATA[<p>It states on Tip #4 that it should only be done in single line instances.</p>
<p>So Tip #4 has cured your issue of attempting multiple lines on something that is <b>solely</b> for single line conditions. It's in the language for a reason ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP Coding Conventions by Chintan Parikh</title>
		<link>http://blog.nexua.org/php-coding-conventions/#comment-1619</link>
		<dc:creator>Chintan Parikh</dc:creator>
		<pubDate>Wed, 18 Jan 2012 08:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nexua.org/?p=629#comment-1619</guid>
		<description>Tip 4 is utterly ridiculous. You should ALWAYS have brackets. I used to do this, and kept messing up when I had to add another line. It&#039;s not worth those few minutes of debugging time, and it doesn&#039;t even look that much better.

I don&#039;t really agree with not putting braces on another line either, but that&#039;s personal preference.</description>
		<content:encoded><![CDATA[<p>Tip 4 is utterly ridiculous. You should ALWAYS have brackets. I used to do this, and kept messing up when I had to add another line. It's not worth those few minutes of debugging time, and it doesn't even look that much better.</p>
<p>I don't really agree with not putting braces on another line either, but that's personal preference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP Coding Conventions by Christopher Cox</title>
		<link>http://blog.nexua.org/php-coding-conventions/#comment-1618</link>
		<dc:creator>Christopher Cox</dc:creator>
		<pubDate>Mon, 09 Jan 2012 06:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nexua.org/?p=629#comment-1618</guid>
		<description>If someone asks me to look at their code and help them with a problem, I refuse to the help them if I spot a hanging bracket. It makes reading it near-on impossible.</description>
		<content:encoded><![CDATA[<p>If someone asks me to look at their code and help them with a problem, I refuse to the help them if I spot a hanging bracket. It makes reading it near-on impossible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

