[bug #32094] [NSString stringByStandardizingPath] doesn't work well with any path beginning with extra slashes

[Richard Frith-Macdonald]

Follow-up Comment #7, bug #32094 (project gnustep):

> Suppose we have got the path string "//path/tofile/" from an external
source.
> Is it an UNC path as a general rule?

Yes ... that's what our documentation says.

> I think somebody who wants standardize that path expects to get
"/path/tofile" 

If you want that behavior, then you should set the library to use strict
'unix' paths as stated in our NSString documentation.  That might make sense
if you are writing unix-only code.

But GNUstep is a cross-platform development framework ... and it's vastly
more likely in general (ie not just the unix world) that //xxx/yyy/ is a well
formed UNC path than a poorly formed unix path,  so you haven't said anything
which suggests that the current behavior is wrong.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32094>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/