And if someone wants to define a "new" and "better" FilePath type, I
would prefer something more abstract, such as a list of Path
components, with functions to serialize it as a String and to parse it
from a String.

A list of path components is just not enough, I'm afraid. What about
extensions? What about drives? If you want an abstract type it will
probably need to be entirely abstract, rather than with some exposed
structure.

Thanks

Neil
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to