<?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 Tom Dalling</title>
	<atom:link href="http://www.tomdalling.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.tomdalling.com</link>
	<description>Thoughts of a software developer</description>
	<lastBuildDate>Sat, 28 Aug 2010 00:49:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Why Inline Comments Are Generally a Bad Idea by Tom Dalling</title>
		<link>http://www.tomdalling.com/coding-styleconventions/why-inline-comments-are-generally-a-bad-idea/comment-page-1#comment-515</link>
		<dc:creator>Tom Dalling</dc:creator>
		<pubDate>Sat, 28 Aug 2010 00:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=208#comment-515</guid>
		<description>Sage advice.</description>
		<content:encoded><![CDATA[<p>Sage advice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Inline Comments Are Generally a Bad Idea by Greg Jorgensen</title>
		<link>http://www.tomdalling.com/coding-styleconventions/why-inline-comments-are-generally-a-bad-idea/comment-page-1#comment-514</link>
		<dc:creator>Greg Jorgensen</dc:creator>
		<pubDate>Fri, 27 Aug 2010 21:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=208#comment-514</guid>
		<description>&quot;Don&#039;t just echo the code with comments -- make every comment count.&quot;nn&quot;Make sure comments and code agree.&quot;nn&quot;Don&#039;t comment bad code -- rewrite it.&quot;nnfrom &quot;The Elements of Programming Style&quot; by Kernighan and Plauger, 1974.</description>
		<content:encoded><![CDATA[<p>&#8220;Don&#8217;t just echo the code with comments &#8212; make every comment count.&#8221;nn&#8221;Make sure comments and code agree.&#8221;nn&#8221;Don&#8217;t comment bad code &#8212; rewrite it.&#8221;nnfrom &#8220;The Elements of Programming Style&#8221; by Kernighan and Plauger, 1974.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Inline Comments Are Generally a Bad Idea by Steven</title>
		<link>http://www.tomdalling.com/coding-styleconventions/why-inline-comments-are-generally-a-bad-idea/comment-page-1#comment-512</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Wed, 25 Aug 2010 04:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=208#comment-512</guid>
		<description>I completely agree.  Here are some of my thoughts about comments.

http://peoplesoftsqr.com/index.php/2009/07/7-comments-about-comments/</description>
		<content:encoded><![CDATA[<p>I completely agree.  Here are some of my thoughts about comments.</p>
<p><a href="http://peoplesoftsqr.com/index.php/2009/07/7-comments-about-comments/" rel="nofollow">http://peoplesoftsqr.com/index.php/2009/07/7-comments-about-comments/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Manufactoria: A Tile-based Programming Game by Ashley Sands</title>
		<link>http://www.tomdalling.com/random-stuff/manufactoria-a-tile-based-programming-game/comment-page-1#comment-511</link>
		<dc:creator>Ashley Sands</dc:creator>
		<pubDate>Wed, 25 Aug 2010 01:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=439#comment-511</guid>
		<description>Wow this is a pretty cool game. A bit confusing to learn though.</description>
		<content:encoded><![CDATA[<p>Wow this is a pretty cool game. A bit confusing to learn though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Implementing Your Own Cocoa Bindings by Tom</title>
		<link>http://www.tomdalling.com/cocoa/implementing-your-own-cocoa-bindings/comment-page-1#comment-471</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 18 Jun 2010 01:13:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=119#comment-471</guid>
		<description>That is fine with me. Good luck with the book.</description>
		<content:encoded><![CDATA[<p>That is fine with me. Good luck with the book.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Implementing Your Own Cocoa Bindings by Aaron Hillegass</title>
		<link>http://www.tomdalling.com/cocoa/implementing-your-own-cocoa-bindings/comment-page-1#comment-470</link>
		<dc:creator>Aaron Hillegass</dc:creator>
		<pubDate>Thu, 17 Jun 2010 18:50:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=119#comment-470</guid>
		<description>Tom, I&#039;m writing a chapter on custom controls in the forthcoming &quot;More Cocoa Programming for Mac OS X&quot;, and  I used this code as a starting point for making a control bindable.  In the end, my code looks a lot like yours.  Is this OK with you?</description>
		<content:encoded><![CDATA[<p>Tom, I&#8217;m writing a chapter on custom controls in the forthcoming &#8220;More Cocoa Programming for Mac OS X&#8221;, and  I used this code as a starting point for making a control bindable.  In the end, my code looks a lot like yours.  Is this OK with you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on For those who have never used Objective C by Erik</title>
		<link>http://www.tomdalling.com/coding-styleconventions/for-those-who-have-never-used-objective-c/comment-page-1#comment-435</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Wed, 28 Apr 2010 02:43:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=411#comment-435</guid>
		<description>It&#039;s a great improvement over C/C++, but Python goes even one better - you can supply the named parameters in any order when invoking the function/method, you don&#039;t have to supply all of them (functions and methods can declare default values for any unsupplied parameter), and you can define functions and methods that take named parameters that don&#039;t exist until they are called - the function body just gets a dictionary that contains whatever name/value pairs were passed to the function. It would be very cool to have this much power in Objective-C.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a great improvement over C/C++, but Python goes even one better &#8211; you can supply the named parameters in any order when invoking the function/method, you don&#8217;t have to supply all of them (functions and methods can declare default values for any unsupplied parameter), and you can define functions and methods that take named parameters that don&#8217;t exist until they are called &#8211; the function body just gets a dictionary that contains whatever name/value pairs were passed to the function. It would be very cool to have this much power in Objective-C.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coding Tip: Have A Single Exit Point by Tom</title>
		<link>http://www.tomdalling.com/coding-tips/coding-tip-have-a-single-exit-point/comment-page-1#comment-428</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Thu, 22 Apr 2010 02:16:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=75#comment-428</guid>
		<description>Strict adherence to the rule can result in complicated nested &#039;if&#039; statements, as the article already mentions, but only in certain cases and there are ways around it. 

It&#039;s an old concept that most people should have heard of by now, but it&#039;s hardly a &quot;dated&quot; concept. I don&#039;t think most people would agree that you can throw return statements anywhere without consequences.</description>
		<content:encoded><![CDATA[<p>Strict adherence to the rule can result in complicated nested &#8216;if&#8217; statements, as the article already mentions, but only in certain cases and there are ways around it. </p>
<p>It&#8217;s an old concept that most people should have heard of by now, but it&#8217;s hardly a &#8220;dated&#8221; concept. I don&#8217;t think most people would agree that you can throw return statements anywhere without consequences.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Coding Tip: Have A Single Exit Point by Steve</title>
		<link>http://www.tomdalling.com/coding-tips/coding-tip-have-a-single-exit-point/comment-page-1#comment-427</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 21 Apr 2010 20:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=75#comment-427</guid>
		<description>The problem with single exit it that it often results in less-readable code because of the complex if/else structure to channel the execution to a single exit point. It&#039;s basically a dated concept.</description>
		<content:encoded><![CDATA[<p>The problem with single exit it that it often results in less-readable code because of the complex if/else structure to channel the execution to a single exit point. It&#8217;s basically a dated concept.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MD5 Hashes in Cocoa by Gordon</title>
		<link>http://www.tomdalling.com/cocoa/md5-hashes-in-cocoa/comment-page-1#comment-412</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Mon, 22 Mar 2010 15:09:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomdalling.com/?p=175#comment-412</guid>
		<description>Thank you. I&#039;ve been scratching my head for a while about this and of all the examples I looked at yours was the easiest to understand.</description>
		<content:encoded><![CDATA[<p>Thank you. I&#8217;ve been scratching my head for a while about this and of all the examples I looked at yours was the easiest to understand.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
