Re: Bug handling UNC pathes on windows in NSString.m/NSFileManager.m

[Roland Schwingel]

Hi...

> > My applied patch fixes this in NSString.m and NSFileManger.m by
> > leaving an additional / in front of the internal representation.
>
> That won't work ... having an initial '//' in the internal
> representation is just wrong
> and would screw up lots of code ... because the slash character is the
> path separator
> and any application splitting the path into components and reassembling
> it would
> get confused.
I yet couldn't find any problems with my version, but your approach
mentioned below is also fine...

> I think that what is needed is some improved way of mapping UNC paths
> to/from
> workable internal names.
>
> I've tried adding a new convention for UNC paths ... the '//' is held
> internally as '~@'
> This matches the existing convention for drive letters ('C:' maps to
> '~C') and is also
> (I hope) readable with respect to network drives .... as
> '//server/directory/file.ext'
> maps to '~@server/directory/file.ext' and '@server' can be read as 'at
> server', which
> should be quite clear.
Sounds to be a good idea... Is it already available in CVS so it can be
tested

Roland, doing a CVS lookup right now...