<?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"
	>
<channel>
	<title>Comments on: Modules</title>
	<atom:link href="http://4.flowsnake.org/archives/64/feed" rel="self" type="application/rss+xml" />
	<link>http://4.flowsnake.org/archives/64</link>
	<description>A Pythoneer's adventures with Chicken Scheme. ^_^ And more.</description>
	<pubDate>Tue, 06 Jan 2009 19:22:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Graham Fawcett</title>
		<link>http://4.flowsnake.org/archives/64#comment-102</link>
		<dc:creator>Graham Fawcett</dc:creator>
		<pubDate>Sat, 16 Feb 2008 03:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/64#comment-102</guid>
		<description>Hans, I echo Houman's statements. It was also hard for me to accept the lack of namespaces in Chicken, but honestly I cannot say it has been a significant problem.

For your *own* code, there are lots of options. The portable syntax-case system (provided as an egg) provides a module system; also, search for 'module' in the eggs list for others. I'm writing my own, just for fun: it's about 100 lines of code and does most of what I'd ever want.</description>
		<content:encoded><![CDATA[<p>Hans, I echo Houman's statements. It was also hard for me to accept the lack of namespaces in Chicken, but honestly I cannot say it has been a significant problem.</p>
<p>For your *own* code, there are lots of options. The portable syntax-case system (provided as an egg) provides a module system; also, search for 'module' in the eggs list for others. I'm writing my own, just for fun: it's about 100 lines of code and does most of what I'd ever want.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Houman Zolfaghari</title>
		<link>http://4.flowsnake.org/archives/64#comment-92</link>
		<dc:creator>Houman Zolfaghari</dc:creator>
		<pubDate>Wed, 13 Feb 2008 22:28:11 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/64#comment-92</guid>
		<description>Three years ago, I had to choose a scheme implementation for a big project (meaning CPU and data intensive, and designed to evolve over many years). For many different reasons, I chose chicken over PLT scheme and gambit (gambit had almost no libraries). My biggest concern with chicken was precisely namespace/modules. 

Now, after 3 intensive chicken years, I'm surprised that I haven't missed them yet.

I should say though that I have yet to see a module system in scheme that solves all the problems while keeping the natural simplicity and bare elegance of scheme . IMHO, all the solutions I've seen are either too arbitrary or too elaborate. I'm not a scheme-at-all-cost proponent, and if I was to abandon the simplicity of scheme, I would as well use CL, Ocaml or Haskell.

I don't write that to enter another boring my-scheme vs your scheme war. I have lots of respect the PLT team's work, as well as each one the scheme implementations. They all have their own strengths and priorities. But this my answer to the question of the necessity of a namespace system.

Many people are using chicken, and producing lots of libraries, and the need for a more elaborate module system was rarely if ever expressed. Maybe we should ask them directly in their in mailing list why and how they can live without it?</description>
		<content:encoded><![CDATA[<p>Three years ago, I had to choose a scheme implementation for a big project (meaning CPU and data intensive, and designed to evolve over many years). For many different reasons, I chose chicken over PLT scheme and gambit (gambit had almost no libraries). My biggest concern with chicken was precisely namespace/modules. </p>
<p>Now, after 3 intensive chicken years, I'm surprised that I haven't missed them yet.</p>
<p>I should say though that I have yet to see a module system in scheme that solves all the problems while keeping the natural simplicity and bare elegance of scheme . IMHO, all the solutions I've seen are either too arbitrary or too elaborate. I'm not a scheme-at-all-cost proponent, and if I was to abandon the simplicity of scheme, I would as well use CL, Ocaml or Haskell.</p>
<p>I don't write that to enter another boring my-scheme vs your scheme war. I have lots of respect the PLT team's work, as well as each one the scheme implementations. They all have their own strengths and priorities. But this my answer to the question of the necessity of a namespace system.</p>
<p>Many people are using chicken, and producing lots of libraries, and the need for a more elaborate module system was rarely if ever expressed. Maybe we should ask them directly in their in mailing list why and how they can live without it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robby Findler</title>
		<link>http://4.flowsnake.org/archives/64#comment-90</link>
		<dc:creator>Robby Findler</dc:creator>
		<pubDate>Wed, 13 Feb 2008 13:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/64#comment-90</guid>
		<description>Well, for one, I would definitely miss modules if they were removed from PLT Scheme. (One thing to keep in mind about the various Schemes out there is that they are really like kissing cousins than actually the same language implemented multiple times.)</description>
		<content:encoded><![CDATA[<p>Well, for one, I would definitely miss modules if they were removed from PLT Scheme. (One thing to keep in mind about the various Schemes out there is that they are really like kissing cousins than actually the same language implemented multiple times.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Axel Søgaard</title>
		<link>http://4.flowsnake.org/archives/64#comment-88</link>
		<dc:creator>Jens Axel Søgaard</dc:creator>
		<pubDate>Wed, 13 Feb 2008 09:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://4.flowsnake.org/archives/64#comment-88</guid>
		<description>Hi Hans,

You can inspect modules, require them dynamically and more in PLT Scheme. For inspection see:

http://pre.plt-scheme.org/docs/html/reference/Expanding_Top-Level_Forms.html#(part~20modinfo)

More tricks can be accomplished with the help of module-&#62;namespace.

Search for module in the pre-release version of the documentation. For a more direct answer, don't hessitate to ask the PLT mailing list.</description>
		<content:encoded><![CDATA[<p>Hi Hans,</p>
<p>You can inspect modules, require them dynamically and more in PLT Scheme. For inspection see:</p>
<p><a href="http://pre.plt-scheme.org/docs/html/reference/Expanding_Top-Level_Forms.html#" rel="nofollow">http://pre.plt-scheme.org/docs/html/reference/Expanding_Top-Level_Forms.html#</a>(part~20modinfo)</p>
<p>More tricks can be accomplished with the help of module-&gt;namespace.</p>
<p>Search for module in the pre-release version of the documentation. For a more direct answer, don't hessitate to ask the PLT mailing list.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
