Hi Daniel, Thanks for the information. However, does this work for a test-compile-debug cycle, or for a modify-interpret cycle? These modules would all be in development. I don't like the idea that I have to 'cabal install' after any change to any module. Is that necessary? Thanks, Mike Daniel Fischer wrote:
Am Samstag 31 Oktober 2009 13:32:51 schrieb Michael Mossey:
I want to have a hierarchy of modules for a local project. Not submitting it to Hackage yet. I just want to refer to my local modules as
Basics.CSound Basics.Node Algo.Fux
etc.
how does one set this up?
Top directory: project.cabal, Setup.hs (module Main where main = defaultMain) Subdirectry Basics: File CSound.hs (module Basics.CSound (exports) where...) File Node.hs (module Basics.Node (exports where...) Subdirectory Algo: File Fux.hs (module Algo.Fux (exports) where...)
cd Top directory cabal install
Thanks, Mike
_______________________________________________ Beginners mailing list Beginners@haskell.org http://www.haskell.org/mailman/listinfo/beginners