On Sat, Mar 24, 2007 at 11:40:37AM -0400, Robert Dockins wrote:
On Saturday 24 March 2007 05:36, Sebastian Sylvan wrote:
The solution is simple:
* If there is a "module M where" clause in the beginning of the file, then it's a "proper" module and shouldn't import the Prelude. * If there is no module declaration then it's a "quick'n dirty script" and should have the Prelude implicitly imported. * Interactive interpreters should probably import the Prelude.
That should take of most issues.
+1 for this opinion. The presence/absence of the "module" declaration seems like a very nice way to separate the student/newbie/just-writing-a-quick-hack class of use cases from the library-maintainer/large-scale-program-author class of use cases.
Thank you Sebastian, you just solved my #1 con. Stefan