System.FilePath survey

Andrew Pimlott andrew at
Wed Feb 8 12:13:35 EST 2006

On Wed, Feb 08, 2006 at 09:39:38AM +0000, Simon Marlow wrote:
> Andrew Pimlott wrote:
> >I don't see why merely introducing an ADT would break anyone's code, as
> >there is no existing standard filepath model, therefore no code to
> >break!
> Sure there's an existing filepath model - the IO module contains this:
>   type FilePath = String

Sorry, I mistyped.  I meant "filepath module", ie the path manipulation

> Yes, but you didn't change FilePath, you added some new file path types 
> and operations, so anyone using your library has to convert from one to 
> the other in order to call exisitng IO operations.

Right, that's an inconvenience.  As I wrote it, though, it's only a
matter of calling "show".


More information about the Libraries mailing list