Re: Process issues (was Re: Lang)
At 2001-03-14 23:55, Marcin 'Qrczak' Kowalczyk wrote:
Should it be required of source files that they explicitly import the Prelude?
Please no. I treat Prelude like elements of syntactic sugar - something available by default, because used almost everywhere. If it's written everywhere, it should not be explicit.
If the Prelude is to be assembled from modules in the library, we need a way of specifying whether or not a given file imports the Prelude. The simplist method would be use of "import Prelude". I don't see it as much more onerous than "#include <stdlib.h>" in a C file. -- Ashley Yakeley, Seattle WA
Mon, 19 Mar 2001 17:51:18 -0800, Ashley Yakeley <ashley@semantic.org> pisze:
If the Prelude is to be assembled from modules in the library, we need a way of specifying whether or not a given file imports the Prelude.
It's extremely rare that a module should not import Prelude.
The simplist method would be use of "import Prelude". I don't see it as much more onerous than "#include <stdlib.h>" in a C file.
<stdlib.h> is not necessary to get arithmetic, builtin type names, numeric literals, and the semicolon which separates statements. -- __("< Marcin Kowalczyk * qrczak@knm.org.pl http://qrczak.ids.net.pl/ \__/ ^^ SYGNATURA ZASTÊPCZA QRCZAK
participants (2)
-
Ashley Yakeley -
qrczak＠knm.org.pl