Re^2: catfile/catdir collapses two leading slashes //

Then I would suggest Files and Filesystems be updated. After all, it did mention "two leading slashes".

I was also confused, because it mentioned "networking and clustering filesystems". These filesystems are not platform-specific. Shouldn't caution be taken every time, since a *nix system could potentially access a Windows network FS?

Comment on Re^2: catfile/catdir collapses two leading slashes //

Replies are listed 'Best First'.
Re^3: catfile/catdir collapses two leading slashes // by ikegami (Patriarch) on Sep 17, 2008 at 22:20 UTC
It's only used by the volume portion of UNC paths. If you were to mount a Windows share onto a unix system, I don't see why you'd use "\\" (or "//") anywhere. For example, if `\\server\docs` was mounted as `/mount/docs`, I presume `\\server\docs\some\path` would be addressed as `/mount/docs/some/path`. "Files and Filesystems" is correct. You shouldn't assume you can't. That doesn't mean you never can.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: catfile/catdir collapses two leading slashes //
by ikegami (Patriarch) on Sep 17, 2008 at 22:20 UTC

It's only used by the volume portion of UNC paths. If you were to mount a Windows share onto a unix system, I don't see why you'd use "\\" (or "//") anywhere. For example, if \\server\docs was mounted as /mount/docs, I presume \\server\docs\some\path would be addressed as /mount/docs/some/path.

"Files and Filesystems" is correct. You shouldn't assume you can't. That doesn't mean you never can.

[reply]
[d/l]
[select]