On Sat, 26 Jun 2010 10:14:50 -0300 Felipe Lessa <[email protected]> wrote: > On Sat, Jun 26, 2010 at 05:01:06PM +0400, Bulat Ziganshin wrote: > > but what you propose cannot be used in Windows at all! while current > > FilePath still works on Unix, with manual filenames en/decoding > > Now we got back on topic! :) > > The FilePath datatype is OS-dependent and making it abstract > should be at least a first step. If you got it from somewhere > else where it is already encoded, then fine. If you need to > construct it, then you need to use a smart constructor. If you > need to show/print it, then you need to convert it to String. > And so on. > It should solve most of problems I believe. But such change will break a lot of programs maybe most of them. How could one introduce such a change? One variant is to create new hierarchy and gradually deprecate old.
Also same problem affect command line arguments and process module. _______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
