
Hi, dear package authors. If you define a useful class, please think twice before you do not export the methods, otherwise something like this will happen: Am Samstag, den 10.11.2012, 21:39 -0800 schrieb David Fox:
It looks like there is an export copy of the whole prettyprint system in template-haskell. I could switch over to that. Oh, and another one in uulib. And also in ansi-wl-pprint. I think I will switch to this last one.
On Sat, Nov 10, 2012 at 6:17 PM, David Fox
wrote: It may belong in Text.PrettyPrint. On Sat, Nov 10, 2012 at 6:16 PM, David Fox
wrote: About as small as a package can get! Yeah, the Pretty class is in haskell-src, but they don't export the pretty method. I will drop them a line, but I sort of assumed they had a reason for doing it that way On Thu, Nov 8, 2012 at 2:02 PM, Joachim Breitner
wrote: Hi David, your pretty-class package is pretty small. In the interest of preventing package proliferation: Have you talked to the maintainers of pretty or haskell-src-exts whether they’d include the class in their code?
Thanks, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata

Hi Joachim, On Sun, Nov 11, 2012 at 02:10:34PM +0100, Joachim Breitner wrote:
dear package authors. If you define a useful class, please think twice before you do not export the methods, otherwise something like this will happen:
I like the way 'Common Lisp' deals with this issue. Exported symbols can be accessed by 'package:symbol' and non exported symbols can be accessed by 'package::symbol'. By using '::' you could still get something done but know, that you did something improper and should consult the appropriate maintainer. You almost have the best of both worlds, because I think that it's a good thing to export as few symbols as possible. Greetings, Daniel
participants (2)
-
Daniel Trstenjak
-
Joachim Breitner