<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Introduction to GObject Introspection</title>
	<atom:link href="http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/</link>
	<description>Just another GNOME Blogs weblog</description>
	<lastBuildDate>Fri, 10 Feb 2012 18:17:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Wolfgang Oertl</title>
		<link>http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/comment-page-1/#comment-113</link>
		<dc:creator>Wolfgang Oertl</dc:creator>
		<pubDate>Mon, 23 Jun 2008 15:20:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/#comment-113</guid>
		<description>Today I found your work on GObject/Gtk language bindings.  I have written lua-gtk, which uses automatically generated information about types, classes etc., but by parsing the output of gccxml.  Quite similar to what you&#039;re working on, isn&#039;t it?  By using compile-time generated minimal perfect hashes with the data, code and data size is kept small. Link to the project&#039;s website included...</description>
		<content:encoded><![CDATA[<p>Today I found your work on GObject/Gtk language bindings.  I have written lua-gtk, which uses automatically generated information about types, classes etc., but by parsing the output of gccxml.  Quite similar to what you&#8217;re working on, isn&#8217;t it?  By using compile-time generated minimal perfect hashes with the data, code and data size is kept small. Link to the project&#8217;s website included&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl Fredrich Bolz</title>
		<link>http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/comment-page-1/#comment-112</link>
		<dc:creator>Carl Fredrich Bolz</dc:creator>
		<pubDate>Wed, 04 Jun 2008 20:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/#comment-112</guid>
		<description>Johan: While I agree that it would be nice to have a way to write extension modules that run with all the various Python implementations, I don&#039;t think it is realistic to use the normal CPython extension modules for that. I don&#039;t think the work of the IronPython guys to support CPython extension modules will be going anywhere. It&#039;s basically one huge hack at the moment and I don&#039;t really see a way to implement it cleanly. The memory model that the extension modules expect (having reference counted C structures) is just too different from that of .NET, which has a safe object model with a moving GC.

Besides, there are quite some extension modules that don&#039;t just use the official API but poke around in the object internals, which obviously cannot be supported at all.

If you want one binding for all runtimes your chances are much better if you do them with ctypes. Sure, ctypes isn&#039;t the nicest thing ever, but at least it is mostly independent of the underlying Python implementation. In fact, both CPython and PyPy already support it and there was a SoC-proposal to implement it for Jython (I don&#039;t remember whether it got accepted).</description>
		<content:encoded><![CDATA[<p>Johan: While I agree that it would be nice to have a way to write extension modules that run with all the various Python implementations, I don&#8217;t think it is realistic to use the normal CPython extension modules for that. I don&#8217;t think the work of the IronPython guys to support CPython extension modules will be going anywhere. It&#8217;s basically one huge hack at the moment and I don&#8217;t really see a way to implement it cleanly. The memory model that the extension modules expect (having reference counted C structures) is just too different from that of .NET, which has a safe object model with a moving GC.</p>
<p>Besides, there are quite some extension modules that don&#8217;t just use the official API but poke around in the object internals, which obviously cannot be supported at all.</p>
<p>If you want one binding for all runtimes your chances are much better if you do them with ctypes. Sure, ctypes isn&#8217;t the nicest thing ever, but at least it is mostly independent of the underlying Python implementation. In fact, both CPython and PyPy already support it and there was a SoC-proposal to implement it for Jython (I don&#8217;t remember whether it got accepted).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johan</title>
		<link>http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/comment-page-1/#comment-111</link>
		<dc:creator>johan</dc:creator>
		<pubDate>Wed, 04 Jun 2008 18:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/#comment-111</guid>
		<description>Carl: Having multiple Gtk+ bindings for reach runtime is not ideal.

PyPy should either follow IronPython&#039;s lead and implement enough of the CPython api to be able to run the extensions specific to CPython or start looking into abstracting the current Gtk+ bindings to be implementation independent.</description>
		<content:encoded><![CDATA[<p>Carl: Having multiple Gtk+ bindings for reach runtime is not ideal.</p>
<p>PyPy should either follow IronPython&#8217;s lead and implement enough of the CPython api to be able to run the extensions specific to CPython or start looking into abstracting the current Gtk+ bindings to be implementation independent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl Fredrich Bolz</title>
		<link>http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/comment-page-1/#comment-110</link>
		<dc:creator>Carl Fredrich Bolz</dc:creator>
		<pubDate>Wed, 04 Jun 2008 16:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/#comment-110</guid>
		<description>Further ahead or not, I am really looking forward to it. It&#039;s the only realistic chance of getting GTK bindings for PyPy. Thanks for doing this work!</description>
		<content:encoded><![CDATA[<p>Further ahead or not, I am really looking forward to it. It&#8217;s the only realistic chance of getting GTK bindings for PyPy. Thanks for doing this work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johan</title>
		<link>http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/comment-page-1/#comment-108</link>
		<dc:creator>johan</dc:creator>
		<pubDate>Mon, 02 Jun 2008 12:25:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/#comment-108</guid>
		<description>Pretty far, we need a proper typelib first. After that pybank needs some love to support that.
Its a worthwhile goal, but its further ahead, I&#039;ll be focusing on languages which generate code for now, such as vala or pygtk.</description>
		<content:encoded><![CDATA[<p>Pretty far, we need a proper typelib first. After that pybank needs some love to support that.<br />
Its a worthwhile goal, but its further ahead, I&#8217;ll be focusing on languages which generate code for now, such as vala or pygtk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kripken</title>
		<link>http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/comment-page-1/#comment-107</link>
		<dc:creator>kripken</dc:creator>
		<pubDate>Mon, 02 Jun 2008 09:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/#comment-107</guid>
		<description>I seem to recall something about using GObject-Introspection to automatically create Python bindings in runtime. Do I remember correctly, and if so, how close are we to getting to that?</description>
		<content:encoded><![CDATA[<p>I seem to recall something about using GObject-Introspection to automatically create Python bindings in runtime. Do I remember correctly, and if so, how close are we to getting to that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lucasr</title>
		<link>http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/comment-page-1/#comment-106</link>
		<dc:creator>lucasr</dc:creator>
		<pubDate>Sun, 01 Jun 2008 19:04:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/#comment-106</guid>
		<description>Dude, this is amazing work! Thanks!</description>
		<content:encoded><![CDATA[<p>Dude, this is amazing work! Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/johan/2008/06/01/introduction-to-gobject-introspection/feed/ ) in 1.19505 seconds, on Feb 12th, 2012 at 6:34 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 12th, 2012 at 7:34 am UTC -->
