Proposal: Add System.FilePath to base

Bulat Ziganshin bulat.ziganshin at
Thu Nov 23 10:20:35 EST 2006

Hello Neil,

Thursday, November 23, 2006, 4:26:50 PM, you wrote:

>> > * Portability, Windows+Linux, GHC+Hugs+Yhc

> functions, it should work. For Portability read "anywhere, any
> compiler". NHC does not work on Windows, so I have not had a chance to
> try it.

ok, you may write "Tested with ... Should work on any H98-compatible

>> if you spend your time working on it, it's better to work in right
>> direction instead of playing ping-pong - now you are moving this
>> module from FilePath library to the Base and in future someone will
>> make just the opposite operation :)

> Whatever happens in the future, I suspect FilePath won't become a
> single standalone library after the base library split happens.

why not start with the library containing single module? in the future
other modules will be added here as well. following this path, you
will not play in move-it move-it game nor make things worser than
in current state

so, i propose to include your lib in the core (or base) library set,
bundle it with ghc and hugs, and host it on like
other ghc-bundled libs

> Given
> that no one knows what will happen, or when, its best that when the
> base library splits the task is "split up the base library", not
> "integrate new modules into a new system which includes the base
> library and other stuff".

we want to split it just because it was inflated so much. so please
don't add even more to this problem. i can only repeat that the
problem lies in the GHC HQ decision which makes impossible to propose
adding FilePath lib to the set of core libs so you are forced to
propose adding it to the base library

Best regards,
 Bulat                            mailto:Bulat.Ziganshin at

More information about the Libraries mailing list