<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>IronPython architecture</title><link>http://blogs.msdn.com/b/johngossman/archive/2005/05/18/419798.aspx</link><description>Chris and I met with Jim Hugunin this morning and got an overview of the IronPython architecture. Which is basically, very simple and straightforward. Like you might expect, it consists of a tokenizer, a parser, a code generator and a library of built</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: IronPython architecture</title><link>http://blogs.msdn.com/b/johngossman/archive/2005/05/18/419798.aspx#419846</link><pubDate>Thu, 19 May 2005 07:26:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:419846</guid><dc:creator>Keith Farmer</dc:creator><description>Doesn't J# get around the name conflict by having its own namespace for J#-specific bits?&lt;br&gt;&lt;br&gt;I can easily see a IronPython namespace, including IronPython.Collections.List.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=419846" width="1" height="1"&gt;</description></item></channel></rss>