<?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"
	>
<channel>
	<title>Comments on: Arc, first impressions</title>
	<atom:link href="http://4.flowsnake.org/archives/52/feed" rel="self" type="application/rss+xml" />
	<link>http://4.flowsnake.org/archives/52</link>
	<description>A Pythoneer's adventures with Chicken Scheme. ^_^ And more.</description>
	<pubDate>Thu, 28 Aug 2008 16:09:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Tim Lovell-Smith</title>
		<link>http://4.flowsnake.org/archives/52#comment-241</link>
		<dc:creator>Tim Lovell-Smith</dc:creator>
		<pubDate>Thu, 29 May 2008 16:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-241</guid>
		<description>Re: 'Odd assignment rules for lists and hash tables.'

If you think about it, hash table lookup (foo bar) IS a function application, i.e. computation of a mapping f(x). It's just different from most other functions in its method of implementation/specification, with e.g. being able to use = to modify the mapping.</description>
		<content:encoded><![CDATA[<p>Re: 'Odd assignment rules for lists and hash tables.'</p>
<p>If you think about it, hash table lookup (foo bar) IS a function application, i.e. computation of a mapping f(x). It's just different from most other functions in its method of implementation/specification, with e.g. being able to use = to modify the mapping.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://4.flowsnake.org/archives/52#comment-169</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Mon, 03 Mar 2008 14:41:57 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-169</guid>
		<description>1.  The overly short names.  If PG wants APL (or J, K, etc.) he knows where to find them.

2.  The irrationality and randomness of the names  Scheme fixed this in R2RS.

3.  The invincible ignorance about Unicode.

4. The belief (also ignorant) that hygienic macros don't matter.  (Hygiene is to macros as lexical binding is to functions -- I suppose we should be glad that Arc doesn't revert to dynamic binding.)

There are probably more, but I stopped looking at this point.</description>
		<content:encoded><![CDATA[<p>1.  The overly short names.  If PG wants APL (or J, K, etc.) he knows where to find them.</p>
<p>2.  The irrationality and randomness of the names  Scheme fixed this in R2RS.</p>
<p>3.  The invincible ignorance about Unicode.</p>
<p>4. The belief (also ignorant) that hygienic macros don't matter.  (Hygiene is to macros as lexical binding is to functions -- I suppose we should be glad that Arc doesn't revert to dynamic binding.)</p>
<p>There are probably more, but I stopped looking at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Arc Debate &#124; LispCast</title>
		<link>http://4.flowsnake.org/archives/52#comment-165</link>
		<dc:creator>The Arc Debate &#124; LispCast</dc:creator>
		<pubDate>Thu, 28 Feb 2008 19:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-165</guid>
		<description>[...] Arc&#8217;s Out Lisp at Light Speed: Arc Brevity Zach&#8217;s Journal - Like a Bi-Metallic Strip Drinkable Chicken » Arc, first impressions (cadr life): Lazy Lists in Arc smuglispweeny: Arc!Cells: It&#8217;s Alive!!! smuglispweeny: [...]</description>
		<content:encoded><![CDATA[<p>[...] Arc&#8217;s Out Lisp at Light Speed: Arc Brevity Zach&#8217;s Journal - Like a Bi-Metallic Strip Drinkable Chicken » Arc, first impressions (cadr life): Lazy Lists in Arc smuglispweeny: Arc!Cells: It&#8217;s Alive!!! smuglispweeny: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ndanger.organism :: blog :: Arc: the blogosphere rages</title>
		<link>http://4.flowsnake.org/archives/52#comment-58</link>
		<dc:creator>ndanger.organism :: blog :: Arc: the blogosphere rages</dc:creator>
		<pubDate>Fri, 01 Feb 2008 05:04:45 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-58</guid>
		<description>[...] Arc, first impressions: Hans is fair and balanced [...]</description>
		<content:encoded><![CDATA[<p>[...] Arc, first impressions: Hans is fair and balanced [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deinst</title>
		<link>http://4.flowsnake.org/archives/52#comment-53</link>
		<dc:creator>Deinst</dc:creator>
		<pubDate>Thu, 31 Jan 2008 19:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-53</guid>
		<description>@Hans:  The major feature that arc fails to take from modern scheme systems is a sane module system.  I find this surprising, given that arc is built atop mzscheme which has a simple (from a user point of view), solid module system.  I suspect that pg would argue that a module system would interfere with the hack and slash philosophy that arc is supposed to engender, but I would argue that any language with macros needs a module system that can give a macro writer the guarantees outlined inin http://citeseer.ist.psu.edu/cache/papers/cs/26833/http:zSzzSzwww.cs.utah.eduzSzpltzSzpublicationszSzmacromod.pdf/flatt02composable.pdf

This is one of the reasons I use mzscheme instead of common lisp.  I'd love a language that had a good module system, macros and access to system threads, and would willingly sacrifice continuations and hygenic macros.</description>
		<content:encoded><![CDATA[<p>@Hans:  The major feature that arc fails to take from modern scheme systems is a sane module system.  I find this surprising, given that arc is built atop mzscheme which has a simple (from a user point of view), solid module system.  I suspect that pg would argue that a module system would interfere with the hack and slash philosophy that arc is supposed to engender, but I would argue that any language with macros needs a module system that can give a macro writer the guarantees outlined inin <a href="http://citeseer.ist.psu.edu/cache/papers/cs/26833/http:zSzzSzwww.cs.utah.eduzSzpltzSzpublicationszSzmacromod.pdf/flatt02composable.pdf" rel="nofollow">http://citeseer.ist.psu.edu/cache/papers/cs/26833/http:zSzzSzwww.cs.utah.eduzSzpltzSzpublicationszSzmacromod.pdf/flatt02composable.pdf</a></p>
<p>This is one of the reasons I use mzscheme instead of common lisp.  I'd love a language that had a good module system, macros and access to system threads, and would willingly sacrifice continuations and hygenic macros.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans Nowak</title>
		<link>http://4.flowsnake.org/archives/52#comment-52</link>
		<dc:creator>Hans Nowak</dc:creator>
		<pubDate>Thu, 31 Jan 2008 16:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-52</guid>
		<description>@John: I am not all that familiar with the history of Scheme (yet); can you give a few examples of things Arc is doing that are (in your opinion) wrong?</description>
		<content:encoded><![CDATA[<p>@John: I am not all that familiar with the history of Scheme (yet); can you give a few examples of things Arc is doing that are (in your opinion) wrong?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans Nowak</title>
		<link>http://4.flowsnake.org/archives/52#comment-51</link>
		<dc:creator>Hans Nowak</dc:creator>
		<pubDate>Thu, 31 Jan 2008 16:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-51</guid>
		<description>@she: Well, it depends on your outlook. Assuming by "such a language" you meant "a Lisp variant", there are various reasons why people would be interesting in learning or trying it, even if they already know a dynamic language like Python or Ruby. Maybe they come from a mathematical background and find a Lisp more appealing than a language with more traditional syntax (although there are functional languages, like OCaml and Haskell, that fit the bill better). Or maybe they keep running into Python/Ruby's limitations and want more flexibility. E.g. in the Arc tutorial there are a few things that languages like Python just cannot do. (Although other Lisps can... this is why most Lispers seem decidedly underwhelmed.)</description>
		<content:encoded><![CDATA[<p>@she: Well, it depends on your outlook. Assuming by "such a language" you meant "a Lisp variant", there are various reasons why people would be interesting in learning or trying it, even if they already know a dynamic language like Python or Ruby. Maybe they come from a mathematical background and find a Lisp more appealing than a language with more traditional syntax (although there are functional languages, like OCaml and Haskell, that fit the bill better). Or maybe they keep running into Python/Ruby's limitations and want more flexibility. E.g. in the Arc tutorial there are a few things that languages like Python just cannot do. (Although other Lisps can... this is why most Lispers seem decidedly underwhelmed.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: she</title>
		<link>http://4.flowsnake.org/archives/52#comment-50</link>
		<dc:creator>she</dc:creator>
		<pubDate>Thu, 31 Jan 2008 15:06:52 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-50</guid>
		<description>The biggest problem is - someone that knows a lot of ruby or python, why would he ever go and try such a language?</description>
		<content:encoded><![CDATA[<p>The biggest problem is - someone that knows a lot of ruby or python, why would he ever go and try such a language?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://4.flowsnake.org/archives/52#comment-49</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Thu, 31 Jan 2008 05:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/52#comment-49</guid>
		<description>Arc: not back to the future, but forward to the past.  It basically takes all the hard-earned lessons of Scheme right up through R6RS and throws them in the trash.</description>
		<content:encoded><![CDATA[<p>Arc: not back to the future, but forward to the past.  It basically takes all the hard-earned lessons of Scheme right up through R6RS and throws them in the trash.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
