<?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: The easy way to keep your code documented</title>
	<atom:link href="http://www.hextudio.com/2007/05/11/the-easy-way-to-keep-your-code-documented/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hextudio.com/2007/05/11/the-easy-way-to-keep-your-code-documented/</link>
	<description></description>
	<lastBuildDate>Thu, 28 May 2009 12:34:01 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tioneB</title>
		<link>http://www.hextudio.com/2007/05/11/the-easy-way-to-keep-your-code-documented/comment-page-1/#comment-133</link>
		<dc:creator>tioneB</dc:creator>
		<pubDate>Wed, 27 Jun 2007 02:44:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.hextudio.com/2007/05/11/the-easy-way-to-keep-your-code-documented/#comment-133</guid>
		<description>&lt;blockquote&gt;When I start I usually add plenty of comments, but later on it always slows down considerably. &lt;/blockquote&gt; hehe yeah me too. I always find myself just trying to make something work, debug, fix, debug, etc.. and then 2-3 days later I&#039;ll have to go back and add comments. It&#039;s a bad habit I&#039;m trying to break... At least Doxygen helps me not to forget about the function header. That&#039;s a start :)

My guess would be that since Torque Script is not very far from the C/C   syntax, doxygen might work.</description>
		<content:encoded><![CDATA[<blockquote><p>When I start I usually add plenty of comments, but later on it always slows down considerably. </p></blockquote>
<p> hehe yeah me too. I always find myself just trying to make something work, debug, fix, debug, etc.. and then 2-3 days later I&#8217;ll have to go back and add comments. It&#8217;s a bad habit I&#8217;m trying to break&#8230; At least Doxygen helps me not to forget about the function header. That&#8217;s a start :)</p>
<p>My guess would be that since Torque Script is not very far from the C/C   syntax, doxygen might work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koen Van Baelen</title>
		<link>http://www.hextudio.com/2007/05/11/the-easy-way-to-keep-your-code-documented/comment-page-1/#comment-131</link>
		<dc:creator>Koen Van Baelen</dc:creator>
		<pubDate>Tue, 26 Jun 2007 21:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.hextudio.com/2007/05/11/the-easy-way-to-keep-your-code-documented/#comment-131</guid>
		<description>Ah, yes, documenting your code! Something I always have to force myself to do. Whenever I start on something I tell myself I&#039;m gonna document everything properly, even though nobody except me will see the code. When I start I usually add plenty of comments, but later on it always slows down considerably. The problem is that in the beginning, your code is easy readable and you know what each line does. Once the project becomes a bit larger, though, it becomes more and more difficult. I wish something like this existed for Torque Game Builder.</description>
		<content:encoded><![CDATA[<p>Ah, yes, documenting your code! Something I always have to force myself to do. Whenever I start on something I tell myself I&#8217;m gonna document everything properly, even though nobody except me will see the code. When I start I usually add plenty of comments, but later on it always slows down considerably. The problem is that in the beginning, your code is easy readable and you know what each line does. Once the project becomes a bit larger, though, it becomes more and more difficult. I wish something like this existed for Torque Game Builder.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
