<?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: My R naming nemesis</title>
	<atom:link href="http://shape-of-code.coding-guidelines.com/2012/12/17/my-r-naming-nemesis/feed/" rel="self" type="application/rss+xml" />
	<link>http://shape-of-code.coding-guidelines.com/2012/12/17/my-r-naming-nemesis/</link>
	<description></description>
	<lastBuildDate>Wed, 01 May 2013 08:59:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: grubert</title>
		<link>http://shape-of-code.coding-guidelines.com/2012/12/17/my-r-naming-nemesis/comment-page-1/#comment-19668</link>
		<dc:creator>grubert</dc:creator>
		<pubDate>Thu, 27 Dec 2012 20:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://shape-of-code.coding-guidelines.com/?p=1216#comment-19668</guid>
		<description>It annoys me when a language designer decides to break with decades of tradition and employ a character for a radically different purpose.

It smacks of arrogance, crankiness, and a lack of genuinely original thought.</description>
		<content:encoded><![CDATA[<p>It annoys me when a language designer decides to break with decades of tradition and employ a character for a radically different purpose.</p>
<p>It smacks of arrogance, crankiness, and a lack of genuinely original thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Jones</title>
		<link>http://shape-of-code.coding-guidelines.com/2012/12/17/my-r-naming-nemesis/comment-page-1/#comment-19653</link>
		<dc:creator>Derek Jones</dc:creator>
		<pubDate>Thu, 20 Dec 2012 11:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://shape-of-code.coding-guidelines.com/?p=1216#comment-19653</guid>
		<description>&lt;a href=&quot;#comment-19651&quot; rel=&quot;nofollow&quot;&gt;@Jens Oehlschlägel &lt;/a&gt; 
That is certainly a useful naming convention and further adds to the feeling that dot is an operator.  However, there is nothing to stop developers using this character in other contexts and I have seen some who seem to use this character where others would use underscore.</description>
		<content:encoded><![CDATA[<p><a href="#comment-19651" rel="nofollow">@Jens Oehlschlägel </a><br />
That is certainly a useful naming convention and further adds to the feeling that dot is an operator.  However, there is nothing to stop developers using this character in other contexts and I have seen some who seem to use this character where others would use underscore.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Oehlschlägel</title>
		<link>http://shape-of-code.coding-guidelines.com/2012/12/17/my-r-naming-nemesis/comment-page-1/#comment-19651</link>
		<dc:creator>Jens Oehlschlägel</dc:creator>
		<pubDate>Wed, 19 Dec 2012 16:12:47 +0000</pubDate>
		<guid isPermaLink="false">http://shape-of-code.coding-guidelines.com/?p=1216#comment-19651</guid>
		<description>It seems to me that what misses in this discussion is the function of dots in R naming: dots in R function names serve as a means to realize R&#039;s oldest class system (S3 classes). A METHODNAME follows the pattern GENERICNAME.CLASSNAME as in summary.lm, where calling GENERICNAME(OBJECT OF CLASSNAME) will dispatch to GENERICNAME.CLASSNAME if present and to GENERICNAME.default otherwise. This allows for something like overloading in other languages.

(resubmitted with placeholders in uppercase since angle brackets dispear here)</description>
		<content:encoded><![CDATA[<p>It seems to me that what misses in this discussion is the function of dots in R naming: dots in R function names serve as a means to realize R&#8217;s oldest class system (S3 classes). A METHODNAME follows the pattern GENERICNAME.CLASSNAME as in summary.lm, where calling GENERICNAME(OBJECT OF CLASSNAME) will dispatch to GENERICNAME.CLASSNAME if present and to GENERICNAME.default otherwise. This allows for something like overloading in other languages.</p>
<p>(resubmitted with placeholders in uppercase since angle brackets dispear here)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dinre</title>
		<link>http://shape-of-code.coding-guidelines.com/2012/12/17/my-r-naming-nemesis/comment-page-1/#comment-19645</link>
		<dc:creator>Dinre</dc:creator>
		<pubDate>Tue, 18 Dec 2012 15:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://shape-of-code.coding-guidelines.com/?p=1216#comment-19645</guid>
		<description>As an engineer myself, I personally don&#039;t have a problem with the &#039;.&#039; in names, but I agree that it can be jarring at first.  However, I think the real issue is to be obviously consistent with whatever naming convention you use.  For instance, I have a problem with &#039;foo&#039; being an object by itself with &#039;foo.bar&#039; being a different and completely unrelated object.  I see this a lot in people&#039;s R code, and it makes reading very difficult for me.  Some popular programming languages use the &#039;.&#039; to denote membership where &#039;foo.bar&#039; indicates [bar] as a member of object/class [foo], so I avoid doing this in my own code.

I&#039;ve read a number of books on R, and everyone seems to use a slightly different naming convention.  The difference between the books I liked and the ones I struggled with had mostly to do with how obvious the naming conventions were.  The more obvious and consistent the naming convention, the easier the code was for me to read.</description>
		<content:encoded><![CDATA[<p>As an engineer myself, I personally don&#8217;t have a problem with the &#8216;.&#8217; in names, but I agree that it can be jarring at first.  However, I think the real issue is to be obviously consistent with whatever naming convention you use.  For instance, I have a problem with &#8216;foo&#8217; being an object by itself with &#8216;foo.bar&#8217; being a different and completely unrelated object.  I see this a lot in people&#8217;s R code, and it makes reading very difficult for me.  Some popular programming languages use the &#8216;.&#8217; to denote membership where &#8216;foo.bar&#8217; indicates [bar] as a member of object/class [foo], so I avoid doing this in my own code.</p>
<p>I&#8217;ve read a number of books on R, and everyone seems to use a slightly different naming convention.  The difference between the books I liked and the ones I struggled with had mostly to do with how obvious the naming conventions were.  The more obvious and consistent the naming convention, the easier the code was for me to read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Young</title>
		<link>http://shape-of-code.coding-guidelines.com/2012/12/17/my-r-naming-nemesis/comment-page-1/#comment-19643</link>
		<dc:creator>Robert Young</dc:creator>
		<pubDate>Tue, 18 Dec 2012 03:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://shape-of-code.coding-guidelines.com/?p=1216#comment-19643</guid>
		<description>Now, how do we get used to the mix of noun.verb and verb.noun naming?</description>
		<content:encoded><![CDATA[<p>Now, how do we get used to the mix of noun.verb and verb.noun naming?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
