Re: [Haskell-cafe] *GROUP HUG*
2011-05-23 22:10 -0700, Gregory Crosswhite: > Hey everyone, > > Okay, this will sound silly, but I ventured into the Scala mailing list > recently and asked an ignorant question on it, and I was shocked when > people reacted not by enlightening me but by jumping on me and reacting > with hostility. I bring this up not to badmouth the Scala community > (they are apparently going through growing pains and will hopefully > mature with time!) but just because it made me appreciate just how > awesome you guys are, so I just feel the need to publicly express my > admiration and thank to everyone on this list for having fostered such > an incredibly professional, fanatically nonhostile, and generally > pleasant place to talk about Haskell!!! > > *GROUP HUG* > > Okay, I'm done now. :-) > > Cheers, > Greg Wow. I subscribed to the list just an hour ago or so, and already receiving hugs! That's kinda... striking, you know. Yay! Newbie hug to everyone too! - max ulidtko signature.asc Description: This is a digitally signed message part ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
[Haskell-cafe] Cabal: wrapping namespace of a package into top-level module
Hi haskell-cafe. I have a package which builds with cabal pretty fine, but there is namespace issue which disturbs me. The problem is that the package exports (to the toplevel namespace!) some modules with fairly general names, like Tests, Basics, Applications. This is probably an oversight of the original package author, and the namespace shouldn't be organised like this... but it is. And I'm looking for a way to avoid potential namespace troubles should I install the package, other than going and reforming the namespace tree myself. What I was thinking about was some cabal option to "wrap" package's namespace into a toplevel module, say "PackageName", so that module Tests could be imported by usual code with `import PackageName.Tests`. Is that possible with cabal? Things are further complicated by the numerous intra-library imports. While the "outside" code refers to a module with PackageName.ModuleName, it would be very desirable that "inside" code used just straight ModuleName. -- Regards, max ulidtko signature.asc Description: This is a digitally signed message part ___ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe