Proposal: Add System.FilePath.Cygwin

Neil Mitchell ndmitchell at
Fri Jun 12 05:24:13 EDT 2009


That's a very good point, and I'm really sure when I started my Cygwin
filepath module there was some critical reason why that was
unacceptable. Unfortunately, I can't remember what that reason was.
I'll try converting my project over to System.FilePath.Posix next
week, and I'll either rediscover the reason, or realise that a Cygwin
module is unnecessary.



On Fri, Jun 5, 2009 at 10:19 AM, Simon Marlow<marlowsd at> wrote:
> On 04/06/2009 14:24, Neil Mitchell wrote:
>> Hi
>> Proposal: Add System.FilePath.Cygwin
>> Ticket at:
>> I propose we add the module System.FilePath.Cygwin to the filepath
>> library. This module would be based on System.FilePath.Windows but
>> with '/' as the preferred path separator, rather than '\\' as for
>> Windows. This module would never be available as System.FilePath, and
>> would always have to be imported specifically if wanted.
>> The desire for this module comes from working with the Cygwin shell,
>> which supports Windows syntax but requires the alternative separator.
>> I have been using such a module for a few months, and find it very
>> useful.
>> There are no backward compatibility concerns, as it is a new separate
>> module.
>> Discussion deadline: 18th June 2009.
> Cygwin is supposed to implement a POSIX-like semantics, so... can't you just
> use System.FilePath.Posix?  If not, why not?
> If it's because you want the library to understand c:/, then perhaps you
> should stick to one style only and use /cygdrive/c instead?
> Cheers,
>        Simon

More information about the Libraries mailing list