<?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 for Sufficiently Small</title>
	<atom:link href="http://www.smallshire.org.uk/sufficientlysmall/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.smallshire.org.uk/sufficientlysmall</link>
	<description>sin(x) = x</description>
	<lastBuildDate>Sat, 12 Jun 2010 02:44:45 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Sun and rain protection with Trimble GPS units by JOSE BOHORQUEZ</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/geoscience/sun-and-rain-protection-with-trimble-gps-units/comment-page-1/#comment-3142</link>
		<dc:creator>JOSE BOHORQUEZ</dc:creator>
		<pubDate>Sat, 12 Jun 2010 02:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?page_id=223#comment-3142</guid>
		<description>I would like to get sun and rain protection with trimble GPS unit. could you sent me to Colombia?

Thanks,

Jose</description>
		<content:encoded><![CDATA[<p>I would like to get sun and rain protection with trimble GPS unit. could you sent me to Colombia?</p>
<p>Thanks,</p>
<p>Jose</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Hindley-Milner type inference implementation in Python by Andy</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2010/04/11/a-hindley-milner-type-inference-implementation-in-python/comment-page-1/#comment-3113</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sat, 01 May 2010 21:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=474#comment-3113</guid>
		<description>&lt;a href=&quot;#comment-3112&quot; rel=&quot;nofollow&quot;&gt;@Robert Smallshire &lt;/a&gt; 
Great! Thanks very much for that, Robert!  
I will indeed credit yourself and the &#039;ancestral&#039; authors. 
I&#039;m looking forward to seeing more great posts like this! ( No pressure though...  :D  )</description>
		<content:encoded><![CDATA[<p><a href="#comment-3112" rel="nofollow">@Robert Smallshire </a><br />
Great! Thanks very much for that, Robert!<br />
I will indeed credit yourself and the &#8216;ancestral&#8217; authors.<br />
I&#8217;m looking forward to seeing more great posts like this! ( No pressure though&#8230;  <img src='http://www.smallshire.org.uk/sufficientlysmall/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' />   )</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Hindley-Milner type inference implementation in Python by Robert Smallshire</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2010/04/11/a-hindley-milner-type-inference-implementation-in-python/comment-page-1/#comment-3112</link>
		<dc:creator>Robert Smallshire</dc:creator>
		<pubDate>Sat, 01 May 2010 10:12:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=474#comment-3112</guid>
		<description>&lt;a href=&quot;#comment-3111&quot; rel=&quot;nofollow&quot;&gt;@Andy &lt;/a&gt; Of course!  You are free to use this code in any way you like.  Attribution of my authorship, and that of the &#039;ancestral&#039; authors would be good sportsmanship, but is not required.  I&#039;m glad you found it useful.</description>
		<content:encoded><![CDATA[<p><a href="#comment-3111" rel="nofollow">@Andy </a> Of course!  You are free to use this code in any way you like.  Attribution of my authorship, and that of the &#8216;ancestral&#8217; authors would be good sportsmanship, but is not required.  I&#8217;m glad you found it useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Hindley-Milner type inference implementation in Python by Andy</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2010/04/11/a-hindley-milner-type-inference-implementation-in-python/comment-page-1/#comment-3111</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sat, 01 May 2010 09:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=474#comment-3111</guid>
		<description>Wow! This is *very* cool, Robert! Many thanks for posting that code!  

I was just wondering - I&#039;m thinking of doing a small public-domain programming language and am thinking of including H.M. type-checking in it. So, would I be able to use the above code in that public-domain language? I&#039;ll certainly acknowledge you as the author, no problem there... :)  

Thanks again for this really interesting post! 
Bye for now - 
- Andy</description>
		<content:encoded><![CDATA[<p>Wow! This is *very* cool, Robert! Many thanks for posting that code!  </p>
<p>I was just wondering &#8211; I&#8217;m thinking of doing a small public-domain programming language and am thinking of including H.M. type-checking in it. So, would I be able to use the above code in that public-domain language? I&#8217;ll certainly acknowledge you as the author, no problem there&#8230; <img src='http://www.smallshire.org.uk/sufficientlysmall/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   </p>
<p>Thanks again for this really interesting post!<br />
Bye for now &#8211;<br />
- Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing Eclipse on Windows Vista by Russell Wallace</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2009/07/27/installing-eclipse-on-windows-vista/comment-page-1/#comment-3078</link>
		<dc:creator>Russell Wallace</dc:creator>
		<pubDate>Tue, 13 Apr 2010 14:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=374#comment-3078</guid>
		<description>But why do you want to do that? It works fine if you just put it in c:\eclipse and there isn&#039;t any hassle.</description>
		<content:encoded><![CDATA[<p>But why do you want to do that? It works fine if you just put it in c:\eclipse and there isn&#8217;t any hassle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BBC Computer 32K by Jon Combe</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2005/11/27/bbc-computer-32k/comment-page-1/#comment-3075</link>
		<dc:creator>Jon Combe</dc:creator>
		<pubDate>Sat, 10 Apr 2010 06:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=4#comment-3075</guid>
		<description>Hi Robert,

we&#039;ve not spoken before but I thought it was interesting that your first paragraph on this page reads very much like my homage to the BBC Computer, and in particular to the game Thrust, here: http://joncom.be/experiments/thrust/

All the very best,
Jon</description>
		<content:encoded><![CDATA[<p>Hi Robert,</p>
<p>we&#8217;ve not spoken before but I thought it was interesting that your first paragraph on this page reads very much like my homage to the BBC Computer, and in particular to the game Thrust, here: <a href="http://joncom.be/experiments/thrust/" rel="nofollow">http://joncom.be/experiments/thrust/</a></p>
<p>All the very best,<br />
Jon</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on OWL BASIC produces its first executable by Les May</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2009/08/04/owl-basic-produces-its-first-executable/comment-page-1/#comment-3030</link>
		<dc:creator>Les May</dc:creator>
		<pubDate>Sat, 13 Feb 2010 19:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=394#comment-3030</guid>
		<description>I&#039;m glad to hear that the BBC Basic/CLR project is going forward and that you have decided to give it a name &#039;Owl Basic&#039; which suggests you are not going to slavishly follow the road to exact compatability with the ARM interpreter.

If I read the last post correctly Owl Basic will permit a space between the keyword &#039;proc&#039; and the procedure name, i.e. def proc DoThis, rather than def proc_DoThis. This is a welcome change and has one very interesting consequence.

I use BBC4W with an external editor, PSPad. This editor allows the use of user produced syntax files and the control over keyword colouring and font. As it operates on whole words it cannot colour the keywork &#039;proc&#039; in proc_DoThis. Allowing a space after proc will allow syntax colouring to be used.

PSPad allows an external compiler (or interpreter) to be called so it will only be a matter of pointing it at the Owl Basic compiler.

If you are willing to go a little bit further in dropping complete compatibility with the ARM interpreter the way functions are defined and called would benefit from a bit of tidying up. In particular an &#039;endfunc&#039; and a specific keyword to return a value from the function would bring it closer to modern ways of doing things. It might mean changing &#039;return&#039; for variables passed by reference to &#039;ref&#039;.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad to hear that the BBC Basic/CLR project is going forward and that you have decided to give it a name &#8216;Owl Basic&#8217; which suggests you are not going to slavishly follow the road to exact compatability with the ARM interpreter.</p>
<p>If I read the last post correctly Owl Basic will permit a space between the keyword &#8216;proc&#8217; and the procedure name, i.e. def proc DoThis, rather than def proc_DoThis. This is a welcome change and has one very interesting consequence.</p>
<p>I use BBC4W with an external editor, PSPad. This editor allows the use of user produced syntax files and the control over keyword colouring and font. As it operates on whole words it cannot colour the keywork &#8216;proc&#8217; in proc_DoThis. Allowing a space after proc will allow syntax colouring to be used.</p>
<p>PSPad allows an external compiler (or interpreter) to be called so it will only be a matter of pointing it at the Owl Basic compiler.</p>
<p>If you are willing to go a little bit further in dropping complete compatibility with the ARM interpreter the way functions are defined and called would benefit from a bit of tidying up. In particular an &#8216;endfunc&#8217; and a specific keyword to return a value from the function would bring it closer to modern ways of doing things. It might mean changing &#8216;return&#8217; for variables passed by reference to &#8216;ref&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Writing a BBC BASIC compiler for the CLR by Les May</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2007/06/10/writing-a-bbc-basic-compiler-for-the-clr/comment-page-1/#comment-3027</link>
		<dc:creator>Les May</dc:creator>
		<pubDate>Sat, 06 Feb 2010 16:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/2007/06/10/writing-a-bbc-basic-compiler-for-the-clr/#comment-3027</guid>
		<description>I invite MUNCH to carefully re-read what I actually said in my posting. I did not say that OBERON does not discard BEBIN/END in control structures. None of the descendents of Pascal implement full closure of control structures. The single word &#039;END&#039; is used to terminate all except the REPEAT..UNTIL loop. If full closure were implemented the examples given would read RECORD..ENDRECORD, FOR..ENDFOR etc. This may be just &#039;syntactic sugar&#039; but it enhances readability. We spend more time reading programs than we do writing them, so readability is important. Lack of ambiguity is the first line of defence against logical errors in a program. 

There is a price to pay for this &#039;verbosity&#039;. It produces larger source files and requires a bit more typing. The latter problem can be overcome by means of a good editor which will check for incorrectly closed control structures and automatically add in the needed terminating word. Interpreters written to the COMAL80 standard accept &#039;NEXT&#039; and replace it with &#039;ENDFOR&#039;. If this could be done 30 years ago it could be done now with compiled languages.

Zonnon corrects one of the unfortunate aspects of MODULA 2 and OBERON which reduce their readability: their insistance on upper case keywords. It does not implement &#039;full closure&#039;. Editors of code for interpreters to the COMAL80 standard accept lower case keyword and silently change it the upper case. I know of only one editor of Component Pascal, a descendent of OBERON 2, which does this. Upper case keywords were fine when everyone used character based displays.

If anyone ever does produce a new COMAL interpreter for the CLR I hope the use of upper case keywords will be dropped. A good syntax highlighting editor would be far better.

One of the factors in making the BBC Basic for Windows so successful is the built in editor. Not perfect but good.</description>
		<content:encoded><![CDATA[<p>I invite MUNCH to carefully re-read what I actually said in my posting. I did not say that OBERON does not discard BEBIN/END in control structures. None of the descendents of Pascal implement full closure of control structures. The single word &#8216;END&#8217; is used to terminate all except the REPEAT..UNTIL loop. If full closure were implemented the examples given would read RECORD..ENDRECORD, FOR..ENDFOR etc. This may be just &#8217;syntactic sugar&#8217; but it enhances readability. We spend more time reading programs than we do writing them, so readability is important. Lack of ambiguity is the first line of defence against logical errors in a program. </p>
<p>There is a price to pay for this &#8216;verbosity&#8217;. It produces larger source files and requires a bit more typing. The latter problem can be overcome by means of a good editor which will check for incorrectly closed control structures and automatically add in the needed terminating word. Interpreters written to the COMAL80 standard accept &#8216;NEXT&#8217; and replace it with &#8216;ENDFOR&#8217;. If this could be done 30 years ago it could be done now with compiled languages.</p>
<p>Zonnon corrects one of the unfortunate aspects of MODULA 2 and OBERON which reduce their readability: their insistance on upper case keywords. It does not implement &#8216;full closure&#8217;. Editors of code for interpreters to the COMAL80 standard accept lower case keyword and silently change it the upper case. I know of only one editor of Component Pascal, a descendent of OBERON 2, which does this. Upper case keywords were fine when everyone used character based displays.</p>
<p>If anyone ever does produce a new COMAL interpreter for the CLR I hope the use of upper case keywords will be dropped. A good syntax highlighting editor would be far better.</p>
<p>One of the factors in making the BBC Basic for Windows so successful is the built in editor. Not perfect but good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Writing a BBC BASIC compiler for the CLR by munch</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2007/06/10/writing-a-bbc-basic-compiler-for-the-clr/comment-page-1/#comment-3025</link>
		<dc:creator>munch</dc:creator>
		<pubDate>Tue, 26 Jan 2010 02:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/2007/06/10/writing-a-bbc-basic-compiler-for-the-clr/#comment-3025</guid>
		<description>Oberon absolutely discards BEGIN/END in control structures.  I&#039;m not sure why Les says it doesn&#039;t, and belies an ignorance of the language from lack of use.  The only use for BEGIN in Oberon is distinguishing program code from declarations in procedures.

RECORD...END, FOR...END, WHILE...END, REPEAT...UNTIL, IF...(ELSE)...(ELSIF)...END, etc.

I invite Les to reconsider his position on Oberon.</description>
		<content:encoded><![CDATA[<p>Oberon absolutely discards BEGIN/END in control structures.  I&#8217;m not sure why Les says it doesn&#8217;t, and belies an ignorance of the language from lack of use.  The only use for BEGIN in Oberon is distinguishing program code from declarations in procedures.</p>
<p>RECORD&#8230;END, FOR&#8230;END, WHILE&#8230;END, REPEAT&#8230;UNTIL, IF&#8230;(ELSE)&#8230;(ELSIF)&#8230;END, etc.</p>
<p>I invite Les to reconsider his position on Oberon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Installing Eclipse on Windows Vista by Greg Fenton</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2009/07/27/installing-eclipse-on-windows-vista/comment-page-1/#comment-2956</link>
		<dc:creator>Greg Fenton</dc:creator>
		<pubDate>Mon, 02 Nov 2009 19:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=374#comment-2956</guid>
		<description>Have you seen this thread:

    http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/</description>
		<content:encoded><![CDATA[<p>Have you seen this thread:</p>
<p>    <a href="http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/" rel="nofollow">http://dev.eclipse.org/blogs/francis/2009/05/24/rcp-p2-vista-and-virtualstore/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
