<?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: deWiTTERS Tao of Coding</title>
	<atom:link href="http://dev.koonsolo.com/21/dewitters-tao-of-coding/feed/" rel="self" type="application/rss+xml" />
	<link>http://dev.koonsolo.com/21/dewitters-tao-of-coding/</link>
	<description>A blog on how to create your own computer games (by Koen Witters)</description>
	<lastBuildDate>Thu, 29 Jul 2010 03:35:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wes</title>
		<link>http://dev.koonsolo.com/21/dewitters-tao-of-coding/comment-page-1/#comment-126</link>
		<dc:creator>Wes</dc:creator>
		<pubDate>Tue, 29 Dec 2009 05:35:22 +0000</pubDate>
		<guid isPermaLink="false">http://dev.koonsolo.com/?p=21#comment-126</guid>
		<description>Great article. My coding style already looks a lot like yours, but you have given me some great ideas. I think I&#039;m going to start using my_ and our_ instead of m_ (for member) and s_ (for shared), for one thing. I also eschew lame verbose comments, but one thing I&#039;ve come to really appreciate is comments that explain a high-level approach.</description>
		<content:encoded><![CDATA[<p>Great article. My coding style already looks a lot like yours, but you have given me some great ideas. I think I&#8217;m going to start using my_ and our_ instead of m_ (for member) and s_ (for shared), for one thing. I also eschew lame verbose comments, but one thing I&#8217;ve come to really appreciate is comments that explain a high-level approach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay</title>
		<link>http://dev.koonsolo.com/21/dewitters-tao-of-coding/comment-page-1/#comment-34</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Fri, 21 Aug 2009 08:22:13 +0000</pubDate>
		<guid isPermaLink="false">http://dev.koonsolo.com/?p=21#comment-34</guid>
		<description>Hi.

Thank you so much for this article.
On the boolean thing, I think that if you borrow the &#039;self&#039; from Python you won&#039;t get the &#039;crazy&#039; words.

if( self_is_sleeping )
    wakeUp()</description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>Thank you so much for this article.<br />
On the boolean thing, I think that if you borrow the &#8217;self&#8217; from Python you won&#8217;t get the &#8216;crazy&#8217; words.</p>
<p>if( self_is_sleeping )<br />
    wakeUp()</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koen Witters</title>
		<link>http://dev.koonsolo.com/21/dewitters-tao-of-coding/comment-page-1/#comment-14</link>
		<dc:creator>Koen Witters</dc:creator>
		<pubDate>Fri, 24 Jul 2009 16:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://dev.koonsolo.com/?p=21#comment-14</guid>
		<description>I receive lots of suggestions by email for the problem when using boolean variables as members, below is a selection of that feedback:
&lt;blockquote&gt;How about relaxing your rule that Booleans must start with is_ or has_ and change it to say that Booleans must start with or contain &quot;is&quot; or &quot;has&quot;.

They you can have &quot;my_age_is_old&quot; and &quot;my_family_has_children&quot;.&lt;/blockquote&gt;

&lt;blockquote&gt;I always use the prefix i_am or i_have as they have the same structure as is_ and has_ except they are in the first person context and shows ownership like my_ does. You may have already thought of this, but it seems to work, at least for me.&lt;/blockquote&gt;

&lt;blockquote&gt;I am wondering if instead of using &quot;my&quot; for the boolean member you use &quot;it&quot;, like you do in for loops for object specification.

Instead of:

    my_is_old, my_has_children

You would have:

    it_is_old, it_has_children

I would assume that since &quot;it&quot; is being used in the variable name and isn&#039;t by itself that &quot;it&quot; would be recognized as a class member instead of as part of a for loop.  Other pronouns would possibly work as well, but they often are gender specific and may not work in the context of the class:

    he_is_old, she_has_children
&lt;/blockquote&gt;

&lt;blockquote&gt;Have you considered doing this?
&quot;i_am_old&quot; or &quot;i_have_children&quot;
&quot;we_are_old&quot; or &quot;we_have_children&quot;
&lt;/blockquote&gt;

&lt;blockquote&gt;I thing the answer is simple: Use no prefixes and always refer to them using this pointer. Like this (pun intended):

if( ! this-&gt;isReadable )
    rewrite();
&lt;/blockquote&gt;

&lt;blockquote&gt;Since you are using is_ and has_ in conjunction with my_ and our_, had you given thought to just applying proper english?  Instead of my_is_old and my_has_children, would it be particularly bad to say i_am_old and i_have_children, or for statics, we_are_old and we_have_children?

I can see the upsides and downsides to this - upside being increased readability and possibly clarity, and it seems that it wouldn&#039;t require any extra thought as we already process language that way.  The biggest downside would be the increased variability, but since you are already using my_/our_ and is_/has_ for different situations...
&lt;/blockquote&gt;

&lt;blockquote&gt;What do u think about using this:
is_my_old and has_my_children
&lt;/blockquote&gt;

&lt;blockquote&gt;How about using &quot;I_am&quot; instead on &quot;is_&quot; and I_have&quot; instead of &quot;has_&quot; for boolean members?

Hence: &quot;I_am_old&quot; instead of &quot;my_is_old&quot;
and &quot;I_have_children&quot; instead of &quot;my_has_children&quot;.
&lt;/blockquote&gt;

My personal favorite is also the one which was suggested the most: i_am_..., i_have_... and we_are_..., we_have_...</description>
		<content:encoded><![CDATA[<p>I receive lots of suggestions by email for the problem when using boolean variables as members, below is a selection of that feedback:</p>
<blockquote><p>How about relaxing your rule that Booleans must start with is_ or has_ and change it to say that Booleans must start with or contain &#8220;is&#8221; or &#8220;has&#8221;.</p>
<p>They you can have &#8220;my_age_is_old&#8221; and &#8220;my_family_has_children&#8221;.</p></blockquote>
<blockquote><p>I always use the prefix i_am or i_have as they have the same structure as is_ and has_ except they are in the first person context and shows ownership like my_ does. You may have already thought of this, but it seems to work, at least for me.</p></blockquote>
<blockquote><p>I am wondering if instead of using &#8220;my&#8221; for the boolean member you use &#8220;it&#8221;, like you do in for loops for object specification.</p>
<p>Instead of:</p>
<p>    my_is_old, my_has_children</p>
<p>You would have:</p>
<p>    it_is_old, it_has_children</p>
<p>I would assume that since &#8220;it&#8221; is being used in the variable name and isn&#8217;t by itself that &#8220;it&#8221; would be recognized as a class member instead of as part of a for loop.  Other pronouns would possibly work as well, but they often are gender specific and may not work in the context of the class:</p>
<p>    he_is_old, she_has_children
</p></blockquote>
<blockquote><p>Have you considered doing this?<br />
&#8220;i_am_old&#8221; or &#8220;i_have_children&#8221;<br />
&#8220;we_are_old&#8221; or &#8220;we_have_children&#8221;
</p></blockquote>
<blockquote><p>I thing the answer is simple: Use no prefixes and always refer to them using this pointer. Like this (pun intended):</p>
<p>if( ! this->isReadable )<br />
    rewrite();
</p></blockquote>
<blockquote><p>Since you are using is_ and has_ in conjunction with my_ and our_, had you given thought to just applying proper english?  Instead of my_is_old and my_has_children, would it be particularly bad to say i_am_old and i_have_children, or for statics, we_are_old and we_have_children?</p>
<p>I can see the upsides and downsides to this &#8211; upside being increased readability and possibly clarity, and it seems that it wouldn&#8217;t require any extra thought as we already process language that way.  The biggest downside would be the increased variability, but since you are already using my_/our_ and is_/has_ for different situations&#8230;
</p></blockquote>
<blockquote><p>What do u think about using this:<br />
is_my_old and has_my_children
</p></blockquote>
<blockquote><p>How about using &#8220;I_am&#8221; instead on &#8220;is_&#8221; and I_have&#8221; instead of &#8220;has_&#8221; for boolean members?</p>
<p>Hence: &#8220;I_am_old&#8221; instead of &#8220;my_is_old&#8221;<br />
and &#8220;I_have_children&#8221; instead of &#8220;my_has_children&#8221;.
</p></blockquote>
<p>My personal favorite is also the one which was suggested the most: i_am_&#8230;, i_have_&#8230; and we_are_&#8230;, we_have_&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
