<?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: C# Default Access Modifier for Class Members &#8211; and drop that private habit!</title>
	<atom:link href="http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/feed/" rel="self" type="application/rss+xml" />
	<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/</link>
	<description>C#, .NET, Ruby, Rails, book reviews, mind hacks, Wing Chun and the occasional personal bit.</description>
	<lastBuildDate>Fri, 18 May 2012 08:47:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Alex Khomich</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-26828</link>
		<dc:creator>Alex Khomich</dc:creator>
		<pubDate>Mon, 04 Oct 2010 05:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-26828</guid>
		<description>Agree with author. But personally I&#039;ve an issue with it because I&#039;m using Java 1/2 of my working time. I skipping to set private in Java too and all of my fields become package protected... Not good :)</description>
		<content:encoded><![CDATA[<p>Agree with author. But personally I've an issue with it because I'm using Java 1/2 of my working time. I skipping to set private in Java too and all of my fields become package protected... Not good <img src='http://jamescrisp.org/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Veli</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-20372</link>
		<dc:creator>Veli</dc:creator>
		<pubDate>Mon, 29 Mar 2010 07:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-20372</guid>
		<description>@Jhon
The &lt;a href=&quot;http://msdn.microsoft.com/en-us/library/ms173121.aspx&quot; rel=&quot;nofollow&quot;&gt;default access modifier&lt;/a&gt; for classes and interfaces is &lt;strong&gt;internal&lt;/strong&gt;.

I also totally agree with Jed Lawrence. Explicit access modifiers are always a good coding practice, easy on the compiler and easy on the eyes when going through the code.</description>
		<content:encoded><![CDATA[<p>@Jhon<br />
The <a href="http://msdn.microsoft.com/en-us/library/ms173121.aspx" rel="nofollow">default access modifier</a> for classes and interfaces is <strong>internal</strong>.</p>
<p>I also totally agree with Jed Lawrence. Explicit access modifiers are always a good coding practice, easy on the compiler and easy on the eyes when going through the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jhon Krammer</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-18668</link>
		<dc:creator>Jhon Krammer</dc:creator>
		<pubDate>Fri, 19 Feb 2010 16:09:03 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-18668</guid>
		<description>default access modifier for CLASS ?</description>
		<content:encoded><![CDATA[<p>default access modifier for CLASS ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Swapnil Lamkane</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-18370</link>
		<dc:creator>Swapnil Lamkane</dc:creator>
		<pubDate>Mon, 15 Feb 2010 08:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-18370</guid>
		<description>Jed Lawrence is right.</description>
		<content:encoded><![CDATA[<p>Jed Lawrence is right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stu</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-12397</link>
		<dc:creator>Stu</dc:creator>
		<pubDate>Tue, 23 Jun 2009 15:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-12397</guid>
		<description>Well I&#039;m agreeing with Jed because I&#039;ve been developing for years and to be honest forgot what the default was which led me to this post. Go standards go!!</description>
		<content:encoded><![CDATA[<p>Well I'm agreeing with Jed because I've been developing for years and to be honest forgot what the default was which led me to this post. Go standards go!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mayur O</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-11232</link>
		<dc:creator>Mayur O</dc:creator>
		<pubDate>Fri, 03 Apr 2009 08:36:17 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-11232</guid>
		<description>Jed I would have to disagree here with you - depending on how much code you have the compiler may get slower and slower if add the default access modifiers in the code.</description>
		<content:encoded><![CDATA[<p>Jed I would have to disagree here with you - depending on how much code you have the compiler may get slower and slower if add the default access modifiers in the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jed Lawrence</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-10665</link>
		<dc:creator>Jed Lawrence</dc:creator>
		<pubDate>Tue, 10 Mar 2009 17:45:36 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-10665</guid>
		<description>I disagree. As the &quot;owner&quot; of the C# and .NET standards document for several organizations, we make it a violation of our standards if any programmer creates any class, struct, enum or interface or any member for same without an access modifier. The inclusion of the access modifier makes it explicit what the programmer&#039;s intentions were which is a fundamental goal of creating standards. When a programmer leaves off an access modifier we do not know whether they did not know what they were doing and they were just lucky that it worked or whether they were assuming that since they know what the &quot;default&quot; is that they are assuming that ALL .NET programmers know what the default is (an absolutely, horrendous assumption). Good programming standards call for always including the access modifier. Most automated code review environments expect the access modifiers.</description>
		<content:encoded><![CDATA[<p>I disagree. As the "owner" of the C# and .NET standards document for several organizations, we make it a violation of our standards if any programmer creates any class, struct, enum or interface or any member for same without an access modifier. The inclusion of the access modifier makes it explicit what the programmer's intentions were which is a fundamental goal of creating standards. When a programmer leaves off an access modifier we do not know whether they did not know what they were doing and they were just lucky that it worked or whether they were assuming that since they know what the "default" is that they are assuming that ALL .NET programmers know what the default is (an absolutely, horrendous assumption). Good programming standards call for always including the access modifier. Most automated code review environments expect the access modifiers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jed Lawrence</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-10664</link>
		<dc:creator>Jed Lawrence</dc:creator>
		<pubDate>Tue, 10 Mar 2009 17:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-10664</guid>
		<description>I disagree. As the &quot;owner&quot; of the C# and .NET standards document for several organizations, we make it a violation of our standards is any programmer creates any class, struct, enum or interface or any member for same without an access modifier. The inclusion of the access modifier makes it explicit what the programmer&#039;s intentions were which is a fundamental goal of creating standards. When a programmer leaves off an access modifier we do not know whether they did not know what they were doing and they were just lucky that it worked or whether they were assuming that since thy know what the &quot;default&quot; is that they are assuming that ALL .NET programmers know what the default is (an absolutely, horrendous assumption). Good programming standards call for always including the access modifier. Most automated code review environments expect the access modifiers.</description>
		<content:encoded><![CDATA[<p>I disagree. As the "owner" of the C# and .NET standards document for several organizations, we make it a violation of our standards is any programmer creates any class, struct, enum or interface or any member for same without an access modifier. The inclusion of the access modifier makes it explicit what the programmer's intentions were which is a fundamental goal of creating standards. When a programmer leaves off an access modifier we do not know whether they did not know what they were doing and they were just lucky that it worked or whether they were assuming that since thy know what the "default" is that they are assuming that ALL .NET programmers know what the default is (an absolutely, horrendous assumption). Good programming standards call for always including the access modifier. Most automated code review environments expect the access modifiers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-5237</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 19 Jun 2008 06:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-5237</guid>
		<description>Glad to see you dont like writing those extra chars either.</description>
		<content:encoded><![CDATA[<p>Glad to see you dont like writing those extra chars either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Dunn</title>
		<link>http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-3854</link>
		<dc:creator>Matt Dunn</dc:creator>
		<pubDate>Tue, 27 May 2008 01:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/2008/05/26/c-default-access-modifier-for-class-members-and-drop-that-private-habit/#comment-3854</guid>
		<description>Nooooooo, but then I have to remember that no access modifier means private! And StyleCop will complain :)

Cheers,
Matt</description>
		<content:encoded><![CDATA[<p>Nooooooo, but then I have to remember that no access modifier means private! And StyleCop will complain <img src='http://jamescrisp.org/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Cheers,<br />
Matt</p>
]]></content:encoded>
	</item>
</channel>
</rss>

