<?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: Python vs Scheme: strings</title>
	<atom:link href="http://4.flowsnake.org/archives/29/feed" rel="self" type="application/rss+xml" />
	<link>http://4.flowsnake.org/archives/29</link>
	<description>A Pythoneer's adventures with Scheme, Clojure and a whole lot more. ^_^</description>
	<lastBuildDate>Sat, 22 May 2010 22:09:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: troels</title>
		<link>http://4.flowsnake.org/archives/29/comment-page-1#comment-48</link>
		<dc:creator>troels</dc:creator>
		<pubDate>Wed, 30 Jan 2008 21:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/29#comment-48</guid>
		<description>I&#039;m fairly new to lisp/scheme myself, and seeing your Python-comparisons made a lot of sense to me. Please post more like this.</description>
		<content:encoded><![CDATA[<p>I&#8217;m fairly new to lisp/scheme myself, and seeing your Python-comparisons made a lot of sense to me. Please post more like this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://4.flowsnake.org/archives/29/comment-page-1#comment-46</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Tue, 29 Jan 2008 18:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/29#comment-46</guid>
		<description>I should also mention that Chicken characters cover the full Unicode range, but how strings are interpreted depends on the egg: by default they are Latin-1 (and Unicode escapes in strings outside the Latin-1 range produce bizarre results), but if you load the utf-8 egg, they are treated as UTF-8, with consequent effects on string-length, string-ref, string-set!, etc.</description>
		<content:encoded><![CDATA[<p>I should also mention that Chicken characters cover the full Unicode range, but how strings are interpreted depends on the egg: by default they are Latin-1 (and Unicode escapes in strings outside the Latin-1 range produce bizarre results), but if you load the utf-8 egg, they are treated as UTF-8, with consequent effects on string-length, string-ref, string-set!, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans Nowak</title>
		<link>http://4.flowsnake.org/archives/29/comment-page-1#comment-31</link>
		<dc:creator>Hans Nowak</dc:creator>
		<pubDate>Sun, 27 Jan 2008 17:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/29#comment-31</guid>
		<description>I think it&#039;s obvious when you think of &quot;+&quot; as &quot;adding two things together&quot; (rather than &quot;a commutative mathematical operation&quot;).</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s obvious when you think of &#8220;+&#8221; as &#8220;adding two things together&#8221; (rather than &#8220;a commutative mathematical operation&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Nowak</title>
		<link>http://4.flowsnake.org/archives/29/comment-page-1#comment-30</link>
		<dc:creator>John Nowak</dc:creator>
		<pubDate>Sun, 27 Jan 2008 16:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/29#comment-30</guid>
		<description>How is using &#039;+&#039; for a non-commutative operation obvious? Here&#039;s what&#039;s not obvious:

&gt;&gt;&gt; a = &quot;foo&quot;
&gt;&gt;&gt; b = &quot;bar&quot;
&gt;&gt;&gt; a + b == b + a
False</description>
		<content:encoded><![CDATA[<p>How is using &#8216;+&#8217; for a non-commutative operation obvious? Here&#8217;s what&#8217;s not obvious:</p>
<p>&gt;&gt;&gt; a = &#8220;foo&#8221;<br />
&gt;&gt;&gt; b = &#8220;bar&#8221;<br />
&gt;&gt;&gt; a + b == b + a<br />
False</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://4.flowsnake.org/archives/29/comment-page-1#comment-29</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Sun, 27 Jan 2008 05:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/29#comment-29</guid>
		<description>The reason R5RS doesn&#039;t have string-{up,down}case is probably that it was assumed those are just lifts of char-{up-down}case over the string, and in ASCII they are.  In the real (Unicode) world, alas, they are not; for example, the uppercase form of &quot;ß&quot; is &quot;SS&quot;.  Consequently, R6RS includes proper string casing functions and warns against using the character functions.</description>
		<content:encoded><![CDATA[<p>The reason R5RS doesn&#8217;t have string-{up,down}case is probably that it was assumed those are just lifts of char-{up-down}case over the string, and in ASCII they are.  In the real (Unicode) world, alas, they are not; for example, the uppercase form of &#8220;ß&#8221; is &#8220;SS&#8221;.  Consequently, R6RS includes proper string casing functions and warns against using the character functions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
