<?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: String compatibility between Python implementations</title>
	<atom:link href="http://www.smallshire.org.uk/sufficientlysmall/2009/06/18/string-compatibility-between-python-implementations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.smallshire.org.uk/sufficientlysmall/2009/06/18/string-compatibility-between-python-implementations/</link>
	<description>sin(x) = x</description>
	<lastBuildDate>Sat, 13 Feb 2010 19:35:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jim Baker</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2009/06/18/string-compatibility-between-python-implementations/comment-page-1/#comment-2561</link>
		<dc:creator>Jim Baker</dc:creator>
		<pubDate>Fri, 19 Jun 2009 17:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=340#comment-2561</guid>
		<description>@David Jones:
I&#039;d recommend using the array module instead of jarray. The array module has two advantages: it&#039;s standard Python, and it interoperates to/from Java array objects. Meanwhile, the jarray module is being phased out, if slowly.</description>
		<content:encoded><![CDATA[<p>@David Jones:<br />
I&#8217;d recommend using the array module instead of jarray. The array module has two advantages: it&#8217;s standard Python, and it interoperates to/from Java array objects. Meanwhile, the jarray module is being phased out, if slowly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Jones</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2009/06/18/string-compatibility-between-python-implementations/comment-page-1/#comment-2559</link>
		<dc:creator>David Jones</dc:creator>
		<pubDate>Fri, 19 Jun 2009 09:48:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=340#comment-2559</guid>
		<description>The repr for jarray.array (in your example) suggests that array.array(&#039;b&#039;) is compatible with jarray.array.  In other words that the arrays you get out of the standard python module for making arrays (array) are in fact the same as native Java arrays.  Which I was just thinking would be a nice feature for interoperability.

Do you know if that is indeed the case?  Can one pass an array.array(&#039;b&#039;) to a Java function that expects a Java array?</description>
		<content:encoded><![CDATA[<p>The repr for jarray.array (in your example) suggests that array.array(&#8217;b') is compatible with jarray.array.  In other words that the arrays you get out of the standard python module for making arrays (array) are in fact the same as native Java arrays.  Which I was just thinking would be a nice feature for interoperability.</p>
<p>Do you know if that is indeed the case?  Can one pass an array.array(&#8217;b') to a Java function that expects a Java array?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Baker</title>
		<link>http://www.smallshire.org.uk/sufficientlysmall/2009/06/18/string-compatibility-between-python-implementations/comment-page-1/#comment-2556</link>
		<dc:creator>Jim Baker</dc:creator>
		<pubDate>Thu, 18 Jun 2009 19:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.smallshire.org.uk/sufficientlysmall/?p=340#comment-2556</guid>
		<description>Please note that the equivalence between the str and unicode types is no longer the case with Jython 2.5. We changed this for compatibility with Python. Also, for Java integration we now convert java.lang.String to/from unicode.

However, we still use String internally to represent str, which requires 2 bytes per actual byte used. This will almost certainly be changed soon to byte[], perhaps as early as 2.5.1, so as to improve performance and reduce memory overhead.</description>
		<content:encoded><![CDATA[<p>Please note that the equivalence between the str and unicode types is no longer the case with Jython 2.5. We changed this for compatibility with Python. Also, for Java integration we now convert java.lang.String to/from unicode.</p>
<p>However, we still use String internally to represent str, which requires 2 bytes per actual byte used. This will almost certainly be changed soon to byte[], perhaps as early as 2.5.1, so as to improve performance and reduce memory overhead.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
