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

[Robert Slover]

I think Sergey may be at least partially correct.

The double-leading-slash is an allowance in POSIX for "implementation defined 
behavior", (such as UNC paths) but for only that specific number of leading 
slashes.  The standard explicitly states that more than two shall be converted 
to a single leading slash.  See the last paragraph of this section:

http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_04_11

I think it is at least valid to consider the argument that GNUstep Base and 
POSIX functions such as realpath() should produce the same results for POSIX 
paths on POSIX-compliant systems.

--Robert

On Jan 11, 2011, at 3:11 AM, Richard Frith-Macdonald wrote:

> 
> Update of bug #32094 (project gnustep):
> 
>                  Status:                    None => Invalid                
>             Open/Closed:                    Open => Closed                 
> 
>    _______________________________________________________
> 
> Follow-up Comment #1:
> 
> The reported behavior is correct/expected (and is the documented behavior)
> ... path handling methods are supposed to permit both unix and windows paths
> by default, but there exists a mechanism to switch to non-portable path
> handling for people who wish to write deliberately non-portable software (eg
> something which will never be used on mswindows).
> 
> See the NSString documentation for more detail.:
> 
> http://www.gnustep.org/resources/documentation/Developer/Base/Reference/NSString.html
> 
> 
>    _______________________________________________________
> 
> Reply to this item at:
> 
>  <http://savannah.gnu.org/bugs/?32094>
> 
> _______________________________________________
>  Message sent via/by Savannah
>  http://savannah.gnu.org/
> 
> 
> _______________________________________________
> Bug-gnustep mailing list
> Bug-gnustep@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-gnustep