This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: UNC Pathname Handling within Applications

Thorsten Haude wrote:

- Is there any standard way to approach this problem? Has it come up
before in other applications?

I don't know why you are even trying to normalize the paths like this. Just hand the thing off to the OS. Usually, both the user and the OS know what it is they are trying to do.

For your program to try to mediate between them, and try to "understand and correct" the user's request is almost always inappropriate.

Don't even try to normalize "\" to "/" or vice-versa. Windows APIs (the low-level ones) know perfectly well how to handle forward-slashes as directory separators..

- Do you know a resource which explains how Posix apps are expected to
handle paths like this?

It doesn't matter. Just pass the names, as is, to the underlying OS API.

POSIX specifically says that *two* leading slashes "implementation defined" behavior, and this is specifically to allow NetBIOS-like (and AFS-like) names in POSIX implementations.

-- Unsubscribe info: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]