Re: NSBundle -initWithPath: warning

[David Ayers]

Richard Frith-Macdonald wrote:

> On 2005-03-31 09:25:17 +0100 David Ayers <d.ayers@inode.at> wrote:
>
> > Richard Frith-Macdonald wrote:
> > [snip]
> >
> > > No ... but I can easily see what the problem is ... '//Local/Library' 
> > > looks like a windows UNC path where 'Local' is the host and 'Library' 
> > > is the share and the actual file is unspecified ... ie it would be a 
> > > relative path on windows.
> >
> >
> > Are you sure this is the behavior we want?
> > The UNC path seems like an absolute path to me, comparable to '/'
>
>
> No ... I'm not sure ... I'm not a windows user.
> I have been treating a UNC path of the form '//host/share' like a 
> drive-relative path of the form 'C:' and assuming that it should be 
> considered 'relative' because it specifies a dvice but not as particular 
> location on the device.  I'm pretty convinced that 'C:' or 'C:file' are 
> relative paths and 'C:/' and 'C:/file' are absolute.  However, it may be 
> that '//host/share' should be treated as equivalent to '//host/share/' 
> ... and both should be treated like '/' on unix.
> Do you know exactly how UNC paths behave?  Is //host/share the same 
> thing as //host/share/ ?

Ahm, no... I just tried a few test on XP comand line and it doesn't 
support UNC paths.  I wasn't aware of the subtle distinction between 
//host/share and //host/share/ (or \\host\share and \\host\share\)

I tried creating a directory named C: in an arbitrary path and it told 
me that C: already existed.  Also trying to cd into either \\host\share 
or \\host\share\ only resulted in a message that UNC Paths are not 
supported by the CMD tool.

Using Start->Run (I believe it would be Run in English) with 
\\host\share\ and \\host\share result in opening an explorer window of 
the same directory.  C: and C:\ behave similarly.

But this are just arbitrary tests and I don't know the details of how 
UNC paths are supposed to be handled and what constitutes a relative path.

Cheers,
David