<?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: Variable Names</title>
	<atom:link href="http://etbe.coker.com.au/2008/07/30/variable-names/feed/" rel="self" type="application/rss+xml" />
	<link>http://etbe.coker.com.au/2008/07/30/variable-names/</link>
	<description>Linux, politics, and other interesting things</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:45:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Richard</title>
		<link>http://etbe.coker.com.au/2008/07/30/variable-names/comment-page-1/#comment-15276</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Mon, 11 Aug 2008 11:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=663#comment-15276</guid>
		<description>John Backus, &quot;The History of Fortran I, II, and III,&quot; IEEE Annals of the History of Computing, vol. 20,  no. 4,  pp. 68-78,  Oct-Dec,  1998

and

Knuth Donald E. and PardoLuis Trabb, &quot;Early Development of Programming Languages,&quot; Encyclopedia of Computer Science and Technology, vol. 7, p. 419.New York: Marcel Dekker, 1977.

should cover your needs for Fortran references, the former is accessible on the web, the latter AFAIK only in paper format</description>
		<content:encoded><![CDATA[<p>John Backus, &#8220;The History of Fortran I, II, and III,&#8221; IEEE Annals of the History of Computing, vol. 20,  no. 4,  pp. 68-78,  Oct-Dec,  1998</p>
<p>and</p>
<p>Knuth Donald E. and PardoLuis Trabb, &#8220;Early Development of Programming Languages,&#8221; Encyclopedia of Computer Science and Technology, vol. 7, p. 419.New York: Marcel Dekker, 1977.</p>
<p>should cover your needs for Fortran references, the former is accessible on the web, the latter AFAIK only in paper format</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: martin</title>
		<link>http://etbe.coker.com.au/2008/07/30/variable-names/comment-page-1/#comment-15135</link>
		<dc:creator>martin</dc:creator>
		<pubDate>Sat, 02 Aug 2008 10:17:24 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=663#comment-15135</guid>
		<description>I believe too that scope is the key. For scopes that are just a few lines it really don&#039;t matter if you can grep for it. 
And then there are problems where you step by step convert something to what you need.
e.g. you have a parameter fileName, and need to build a chain of new variables to use it in the function. sure i could name them fileNameFile, fileNameInputStream, fileNameReader, but that&#039;s really useless clutter, in such chains it&#039;s often much more useful to name the first variable readable and the last (if it&#039;s scope is big enough) and give the one&#039;s in the middle just &quot;type code&quot; variable names from the classes of the instances they refer to.</description>
		<content:encoded><![CDATA[<p>I believe too that scope is the key. For scopes that are just a few lines it really don&#8217;t matter if you can grep for it.<br />
And then there are problems where you step by step convert something to what you need.<br />
e.g. you have a parameter fileName, and need to build a chain of new variables to use it in the function. sure i could name them fileNameFile, fileNameInputStream, fileNameReader, but that&#8217;s really useless clutter, in such chains it&#8217;s often much more useful to name the first variable readable and the last (if it&#8217;s scope is big enough) and give the one&#8217;s in the middle just &#8220;type code&#8221; variable names from the classes of the instances they refer to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rchrd</title>
		<link>http://etbe.coker.com.au/2008/07/30/variable-names/comment-page-1/#comment-15089</link>
		<dc:creator>rchrd</dc:creator>
		<pubDate>Wed, 30 Jul 2008 23:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=663#comment-15089</guid>
		<description>In any case, Fortran allows one to say that 
&quot;GOD is REAL, NIRVANA IS NOT&quot;</description>
		<content:encoded><![CDATA[<p>In any case, Fortran allows one to say that<br />
&#8220;GOD is REAL, NIRVANA IS NOT&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rchrd</title>
		<link>http://etbe.coker.com.au/2008/07/30/variable-names/comment-page-1/#comment-15088</link>
		<dc:creator>rchrd</dc:creator>
		<pubDate>Wed, 30 Jul 2008 23:40:56 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=663#comment-15088</guid>
		<description>The reason why i, j, k, l, m, n were chosen as integer variable names (or names beginning with those letters) in Fortran was because it is that way in written mathematics.

When you write a summation with a sigma sign, the summation variable is usually &quot;i&quot; or &quot;k&quot; and the upper limit is usually &quot;n&quot;.  Go check any calculus textbook. 

A polynomial&#039;s coefficients are usually expressed as integer subscripts, so a sub i (I can&#039;t write it that way in this comment) gets converted to A(I) in Fortran. This would be the i-th coefficient in a polynomial like

A1*X + A2*X**2 + ...

And if a DO loop is analogous to a summation, then:

  DO 1 I=1,N
  Y = Y + A(I)*X**I
1 CONTINUE

is the way to write the evaluation of a polynomial.  (Remember, Fortran arrays start at 1).

Fortran was designed to do numerical calculations  ... FORmula TRANslation.</description>
		<content:encoded><![CDATA[<p>The reason why i, j, k, l, m, n were chosen as integer variable names (or names beginning with those letters) in Fortran was because it is that way in written mathematics.</p>
<p>When you write a summation with a sigma sign, the summation variable is usually &#8220;i&#8221; or &#8220;k&#8221; and the upper limit is usually &#8220;n&#8221;.  Go check any calculus textbook. </p>
<p>A polynomial&#8217;s coefficients are usually expressed as integer subscripts, so a sub i (I can&#8217;t write it that way in this comment) gets converted to A(I) in Fortran. This would be the i-th coefficient in a polynomial like</p>
<p>A1*X + A2*X**2 + &#8230;</p>
<p>And if a DO loop is analogous to a summation, then:</p>
<p>  DO 1 I=1,N<br />
  Y = Y + A(I)*X**I<br />
1 CONTINUE</p>
<p>is the way to write the evaluation of a polynomial.  (Remember, Fortran arrays start at 1).</p>
<p>Fortran was designed to do numerical calculations  &#8230; FORmula TRANslation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andres Salomon</title>
		<link>http://etbe.coker.com.au/2008/07/30/variable-names/comment-page-1/#comment-15087</link>
		<dc:creator>Andres Salomon</dc:creator>
		<pubDate>Wed, 30 Jul 2008 21:13:16 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=663#comment-15087</guid>
		<description>If someone turns it into a 400-line block: shoot them.  There&#039;s a reason why programming languages support functions.</description>
		<content:encoded><![CDATA[<p>If someone turns it into a 400-line block: shoot them.  There&#8217;s a reason why programming languages support functions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Vega</title>
		<link>http://etbe.coker.com.au/2008/07/30/variable-names/comment-page-1/#comment-15084</link>
		<dc:creator>James Vega</dc:creator>
		<pubDate>Wed, 30 Jul 2008 14:57:19 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=663#comment-15084</guid>
		<description>Paul: The difference between vim and vim-nox is that vim-nox includes the Perl, Python, Ruby, and TCL language bindings.  The basic progression in the packaging is: vim-tiny (minimal), vim (base feature set which all packages aside from vim-tiny build on), vim-nox (vim + language bindings), vim-{gtk,gnome,lesstif} (vim-nox + gvim).

Russell: As indicated in my response to Paul, the vim package does indeed have syntax highlighting available.  None of the packages turn on syntax highlighting by default, so there&#039;s a discrepancy in user-side configuration somewhere (possibly &quot;syntax on&quot; is only in your ~/.gvimrc).  Also, vim-{full,perl,ruby,python,tcl} are just transitional packages as of Lenny.

James (with my pkg-vim maintainer hat on)</description>
		<content:encoded><![CDATA[<p>Paul: The difference between vim and vim-nox is that vim-nox includes the Perl, Python, Ruby, and TCL language bindings.  The basic progression in the packaging is: vim-tiny (minimal), vim (base feature set which all packages aside from vim-tiny build on), vim-nox (vim + language bindings), vim-{gtk,gnome,lesstif} (vim-nox + gvim).</p>
<p>Russell: As indicated in my response to Paul, the vim package does indeed have syntax highlighting available.  None of the packages turn on syntax highlighting by default, so there&#8217;s a discrepancy in user-side configuration somewhere (possibly &#8220;syntax on&#8221; is only in your ~/.gvimrc).  Also, vim-{full,perl,ruby,python,tcl} are just transitional packages as of Lenny.</p>
<p>James (with my pkg-vim maintainer hat on)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

