System.FilePath propsal (Was: Cabal feedback notes)

[Krasimir Angelov]

--- Andrew Pimlott <andrew at pimlott.net> wrote:

> On Tue, Oct 26, 2004 at 06:33:43AM -0700, Krasimir
> Angelov wrote:
> > Ok. Here is one concrete proposal for
> System.FilePath.
> 
> I want to reiterate my earlier comments.
> 
>    
>
http://www.haskell.org/pipermail/libraries/2004-June/002283.html
> 
> Andrew
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
> 


>From your comments:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> You don't seem to address the problem of volumes or
> drives (a:, c:).  I don't think you can punt this.

The drives are handled implicitly. They are always
part of directory name. If you think that it is useful
to make this explicitly then you would suggest a
concrete API and possible use cases for it.

> Be very explicit in the documentation about what 
> your model of a path is. Most libraries implictly 
> rely upon some form of unix conventions, without 
> pinning them down.  I find it hard to use File::Spec
> without trial and error.

The Haddock documentation can be improved.

> Finally, it's probably not acceptible for 
> a "production library" to hard-code the path 
> separator by platform.  There will have to be a way
> to manipulate foreign paths.

It is not hard to split System.FilePath to
System.FilePath.Posix and System.FilePath.Windows. I
will do that if other people also agree on that.

Cheers,
  Krasimir



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail