Taking a lesson from relational databases, I'd put it in 5-normal form:
a separate module importing its two dependencies.
Don't forget the 2nd law of thermodynamics: no 4-line file will stay 4
lines long after repeated code iterations. You might as well plan for
the inevitable.
If it's too annoying to wait for that inevitability, try commenting the
hell out of it until it has a respectable number of lines.
Dan
Neil Mitchell wrote:
Hi
I currently maintain two libraries, TagSoup which defines the Tag data
type, and BinaryDefer, which defines the BinaryDefer class. If I
wanted to include an instance for BinaryDefer Tag, where would I put
it?
Putting it in either library introduces an artificial dependency on
the other. Putting it in a separate libary makes the library about 4
lines long and is just annoying. Putting it in the individual
application(s) is exactly what libraries were designed to avoid.
Is there a solution?
Thanks
Neil
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
