How do people who like unit testing / property testing deal with export lists?

I often find that I do want an export list to reduce clutter in the
finished code, but for testing I'd like to expose everything in a
module.  Is there a nice way to deal with this (using the C
pre-processor would not qualify as "nice" ;-)?
Maybe there's a switch that causes GHC to simply ignore the export
list of a module and export everything?

/M

-- 
Magnus Therning                        (OpenPGP: 0xAB4DFBA4)
magnus@therning.org          Jabber: magnus@therning.org
http://therning.org/magnus         identi.ca|twitter: magthe
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to