Jean-Philippe Bernardy wrote: > As for > 1: if you want the Interactive mode configurable, it has to depend on Config > in
Okay, then I guess the modules that behave that way should be changed to first search the modeTable in Config whether a mode of that name(or some other identifier) is already in there and use that instead, if that's the case. If one could assume that every module(except probably some special cases) uses such a mechanism, then my point is moot. I guess I'll try to implement your suggested solution then. > The only reason was to limit the number of hs-boot files and usage of > the newtype > deriving construct. I'm unsure if this last point will allow you to > even split it in a separate module. > > Another take on the issue is to rename Yi.Keymap into Yi.Action. This might be no longer related to my particular problem, but: Why would that newtype deriving prevent moving these types(that are needed in Config) to another module, say Yi.Action, and keep it separate from the actual keymap-related code(that needs stuff from Config) in Keymap.hs? That way the new module wouldn't have to depend on Config and we would get around this dependency cycle in the first place. Thanks for your clarifications. --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
