On Wed, Mar 25, 2009 at 1:13 AM, steffen.sier...@googlemail.com <steffen.sier...@googlemail.com> wrote: > > >> > * added experimental support for adding custom modules in ~/.yi/ for use >> > in yi.hs >> >> > This patch allows placing further private modules in ~/.yi/ to be used >> > by yi.hs and recompile configuration everytime one Source-file was >> > touched. >> >> > This patch is kind of controversial since: >> > - removed "-i" flag from ghc --make to find all modules >> >> I think putting the current directory in the search path is definitely >> not acceptable: it's hard enough to tell which version of the code is >> running. If it depends on `pwd` it's going to be even worse. It would >> be ok to add a fixed path to the search path tough. >> > It's not depending on `pwd`. The code already ensures that ghc is > running inside > $HOME/.yi and therefore all additional modules must reside in > $HOME/.yi
I see. This has a slight problem still: on case-insensitive systems (Mac OS), the configuration file (yi.hs) is confused with the top-level Yi module. So either a sub-directory should be created, or the configuration file renamed. > >> > - ghc --make is run on every startup, since ghc --make >> > tests for file changes obeying module dependencies >> >> How slow/fast is this? >> > On my system it seems to be fast, but it would be nice to measure how > fast/slow it really is thus others may test it too. > Is there a simple way of measuring startup time? I suggest you submit this part in a separate patch. We can them apply it and let people test it. If nobody complains about the speed we just keep it. Cheers, JP. --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
