<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Language runtime independance</title>
	<link>http://blog.floopily.org/2008/01/28/language-runtime-independance/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 04:34:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: rob</title>
		<link>http://blog.floopily.org/2008/01/28/language-runtime-independance/#comment-195</link>
		<dc:creator>rob</dc:creator>
		<pubDate>Mon, 28 Jan 2008 14:19:44 +0000</pubDate>
		<guid>http://blog.floopily.org/2008/01/28/language-runtime-independance/#comment-195</guid>
		<description>@cfbolz:
Yes indeed! I think the point I failed to articulate is that PyPy may be a better approch to solving the problem that Colin was addressing than having a common hand-written vm.</description>
		<content:encoded><![CDATA[<p>@cfbolz:<br />
Yes indeed! I think the point I failed to articulate is that PyPy may be a better approch to solving the problem that Colin was addressing than having a common hand-written vm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cfbolz</title>
		<link>http://blog.floopily.org/2008/01/28/language-runtime-independance/#comment-194</link>
		<dc:creator>cfbolz</dc:creator>
		<pubDate>Mon, 28 Jan 2008 14:09:45 +0000</pubDate>
		<guid>http://blog.floopily.org/2008/01/28/language-runtime-independance/#comment-194</guid>
		<description>All this is true, I just want to stress that PyPy does not write a common VM for all these languages at all. Instead we try to share as much infrastructure (GCs, access to OS services, bits of the JIT compiler) between these language implementations without artificially imposing any common runtime. Indeed, one of our main claims is that it is generally a bit idea to write VMs (let the computer do it for you instead):

http://dyla2007.unibe.ch/?download=dyla07-HowToNotWriteVMs.pdf

About language interoperation, PyPy does not work on that so far. I guess PyPy could be a nice environment for experimenting with that as soon as more of our interpreters become mature (and when we get some actual users :-) ).</description>
		<content:encoded><![CDATA[<p>All this is true, I just want to stress that PyPy does not write a common VM for all these languages at all. Instead we try to share as much infrastructure (GCs, access to OS services, bits of the JIT compiler) between these language implementations without artificially imposing any common runtime. Indeed, one of our main claims is that it is generally a bit idea to write VMs (let the computer do it for you instead):</p>
<p><a href="http://dyla2007.unibe.ch/?download=dyla07-HowToNotWriteVMs.pdf" rel="nofollow">http://dyla2007.unibe.ch/?download=dyla07-HowToNotWriteVMs.pdf</a></p>
<p>About language interoperation, PyPy does not work on that so far. I guess PyPy could be a nice environment for experimenting with that as soon as more of our interpreters become mature (and when we get some actual users <img src='http://blog.floopily.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> ).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
