<br><div class="gmail_quote">On Fri, May 9, 2008 at 10:02 AM, Andrew Coppin <<a href="mailto:andrewcoppin@btinternet.com">andrewcoppin@btinternet.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Darrin Thompson wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2008/5/8 Donnie Jones <<a href="mailto:donnie@darthik.com" target="_blank">donnie@darthik.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would be interested to see an article on Haskell in the same light as this<br>
Ocaml article, aka a constructive criticism of Haskell.<br>
<br>
<br>
</blockquote>
<br>
<a href="http://www.drmaciver.com/2008/02/tell-us-why-your-language-sucks/" target="_blank">http://www.drmaciver.com/2008/02/tell-us-why-your-language-sucks/</a><br>
<br>
</blockquote>
<br>
Impressive. He thought of a whole bunch of stuff I hadn't thought of.<br>
<br>
While I'm here - I'm aware of how you control importing [or not] from the Prelude. Is there a way that I can, for example, import all the stuff like the basic types, classes, etc., but *not* all the list-related stuff? Or is the Prelude not that modular?<br>
</blockquote><div><br>Not only is the Prelude not that modular, there's not really any mechanism to make it so. There's no way to partition an export list in such a way that whole chunks of it can be imported/not imported at a go. Would that be a nice feature? I don't know, possibly.<br>
<br>-Brent<br></div></div>