Hello Lemmih, Wednesday, March 22, 2006, 9:07:47 PM, you wrote:
L> In particular, I've been thinking about refactoring out the L> preprocessing to allow a full compilation plan to be generated before L> it's executed, and, consequently, hoisting 'getOutputFilename' out of L> the inner loop. one time i planned to write tar-like tool in such completely functional way: the whole work seen as several "passes" which just transforms information. first pass converts cmdline to the "job description", second converts this description to the structure of builded archive, next pass converts this structure to the sequence of i/o operations and last pass just performs these operations. the final program was not such straightforward, but at least such functional vision helped me to develop program structure in more regular way one thing about GHC what i will be glad to see is using WIDE compilation instead of DEEP one. i mean that after GHC analyzed dependencies and decided which files to compile, it should on first pass syntax-analyze all compiled files, at next pass it should perform typechecking in all files and so on. this will help to find errors faster (but on other side will require more memory) -- Best regards, Bulat mailto:[EMAIL PROTECTED] _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
