> class Serialize a where > read :: FilePath -> IO a > write :: a -> FilePath -> IO ()
I understand that approach. My feeling on the matter is that it is a bad idea if taken to its logical conclusion. Eventually every library that could possibly need to serialize data would end up with its own typeclass for serialization. It is much better, in my opinion, to say "use text, or use binary". And it bears pointing out that Data.Binary requires an instance declaration for the 'Binary' typeclass, and (I believe) there isn't really anything preventing you from outputting whatever arbitrary data you desire using it. I am generally in favor of allowing more customization to the user of a library, but can you name some specific situations in which neither Read/Show nor Data.Binary would suffice? - Will Donnelly --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
