Modules and their explicit export lists (are an annoyance)
aslatter at gmail.com
Mon Jun 21 19:37:31 EDT 2010
Aarg, the "send" button is way to toucy on my mail client.
I was trying to say that you should contact the community or the package
maintainer to try and work something out before forking.
It is true that all of this is usually free software, but it is a lot easier
to manage if there aren't a large number of packages out there of dubious
status regarding how and why they are maintained.
Are there any specific packages you're having trouble with at the moment?
On Jun 21, 2010 6:34 PM, "Antoine Latter" <aslatter at gmail.com> wrote:
I encourage you to email the lists or the library maintainer before forking
- ther might be ways to solve your problem in a different way or to get the
> On Jun 21, 2010 4:20 PM, "Christian Höner zu Siederdissen" <
choener at tbi.univie.ac.at> wrote:
> > played around with a library that uses an explicit export list. While
> there are reasons for havi...
> > But the more important thing is, that it makes extending module
> functionality a pain (eg. if a c...
> > Btw. there are libraries, where an explicit export list is used, that
> export the right amount of...
> > Glasgow-haskell-users mailing list
> > Glasgow-haskell-users at haskell.org
> Glasgow-haskell-users mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Glasgow-haskell-users