<?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>Commenti a: EEG!!</title>
	<atom:link href="http://www.mastrogippo.it/2009/12/eeg/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mastrogippo.it/2009/12/eeg/</link>
	<description>Alla prossima puntata!</description>
	<lastBuildDate>Sat, 24 Jul 2010 08:01:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Di: Mastro Gippo</title>
		<link>http://www.mastrogippo.it/2009/12/eeg/comment-page-1/#comment-2693</link>
		<dc:creator>Mastro Gippo</dc:creator>
		<pubDate>Sat, 24 Jul 2010 08:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mastrogippo.it/?p=161#comment-2693</guid>
		<description>Hi, thank you for your feedback. I have always left out brackets for single lines of code, because I like it this way and I think it&#039;s more readable. The indentation reminds me that I have to add them if I add more lines. In years of programming I&#039;ve never been bitten by this bug, so I guess this works for me... 

I also like to put {} in their own lines, as a habit. I never knew it was called &quot;Allman style&quot;, but since &quot;Proponents of this style often cite its use by ANSI and in other standards as justification for its adoption.&quot;, I guess that I use it because ANSI uses it! :)</description>
		<content:encoded><![CDATA[<p>Hi, thank you for your feedback. I have always left out brackets for single lines of code, because I like it this way and I think it&#8217;s more readable. The indentation reminds me that I have to add them if I add more lines. In years of programming I&#8217;ve never been bitten by this bug, so I guess this works for me&#8230; </p>
<p>I also like to put {} in their own lines, as a habit. I never knew it was called &#8220;Allman style&#8221;, but since &#8220;Proponents of this style often cite its use by ANSI and in other standards as justification for its adoption.&#8221;, I guess that I use it because ANSI uses it! <img src='http://www.mastrogippo.it/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Di: Ray</title>
		<link>http://www.mastrogippo.it/2009/12/eeg/comment-page-1/#comment-2692</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Sat, 24 Jul 2010 00:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mastrogippo.it/?p=161#comment-2692</guid>
		<description>I had a quick look at your source for the EEG project...  

a few comments... 

you should ALWAYS put  { } for all if/while/for, even if there is only 1 command in them. Thus is you ever modify you code in the future and add another command, you will not make a bug that is VERY hard to find...

so this is wrong
if (a==1) {
   a++;
   b++;
} else
   B++;

this is better
if (a==1) {
   a++;
   b++;
} else {
   b++;
}

Also i find it is better to put the { on the same line as the if/for/while  and the } on it own line...  then it is easier to find the } for a statement and the number of lines on the screen is less... and you can see more of what you are writting</description>
		<content:encoded><![CDATA[<p>I had a quick look at your source for the EEG project&#8230;  </p>
<p>a few comments&#8230; </p>
<p>you should ALWAYS put  { } for all if/while/for, even if there is only 1 command in them. Thus is you ever modify you code in the future and add another command, you will not make a bug that is VERY hard to find&#8230;</p>
<p>so this is wrong<br />
if (a==1) {<br />
   a++;<br />
   b++;<br />
} else<br />
   B++;</p>
<p>this is better<br />
if (a==1) {<br />
   a++;<br />
   b++;<br />
} else {<br />
   b++;<br />
}</p>
<p>Also i find it is better to put the { on the same line as the if/for/while  and the } on it own line&#8230;  then it is easier to find the } for a statement and the number of lines on the screen is less&#8230; and you can see more of what you are writting</p>
]]></content:encoded>
	</item>
</channel>
</rss>
