hirarchical modules

[Hal Daume III]

This was brought up before:

  http://www.haskell.org/pipermail/libraries/2002-February/000552.html

and then again before that I think I wrote something about it, but can't
find the message.  Needless to say, I think this would be *very* nice, but
there didn't seem to be support from the powers that be.

As for moving things around, the suggestion I got was to use a quick
'grep' to change the module names :).  Very efficient.

 - Hal

--
 Hal Daume III                                   | hdaume@isi.edu
 "Arrest this man, he talks in maths."           | www.isi.edu/~hdaume

On Wed, 28 May 2003, Iavor Diatchki wrote:

> hello,
> 
> i was wondering how final is the design of the hirarchical module system 
> for haskell?  i have been working on the monad library for the past week 
> or so and this is my first experience with the hirarchical module system
> in a real project. i must say that i find it very cumbersome.
> 
> here is why:  the whole monadic library is in the same directory, but 
> since there is no way to use relative names, all the imports use the 
> rather long fully qualified name.  things like:
> 
> import Control.Monad.X.ReaderT
> 
> are very common. and if the hirarchy gets deeper, names will get longer.
> while the verbosilty is annoying there is a more serious problem. 
> moving code around is very work intensive (and error prone).  for 
> example, when i decide that what i have is stable enough i'd like to 
> move it to the Control.Monad part of the library (i.e. get rid of the 
> X).  that means that i have to go and change all the imports, and all 
> the module names.
> 
> of course i have a haskell lexer at my disposition so i have a little 
> program to do that for me, but that solution seems very unsatisfactory.
> 
> and there seems to be a rather obvious solution to this problem:
> 1. allow for imports relative to the location of the importing module
> 2. remove the requirement that the path to a module is hardcoded in the 
> module name.
> 
> i am now hoping that someone will say: yes we already tought of that and 
> it is indeed supported...
> any thoughts?
> 
> bye
> iavor
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Libraries mailing list
> Libraries@haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>