This is the mail archive of the
mailing list for the Cygwin project.
Re: Problematic interpretion of paths starting with double slashes
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Wed, 13 Jun 2018 19:08:18 +0200
- Subject: Re: Problematic interpretion of paths starting with double slashes
- References: <trinity-82173dac-d842-4a87-8d1f-bed9a958d178-1528793630066@3c-app-gmx-bs08> <firstname.lastname@example.org> <trinity-2aa37c55-032a-4631-9d8f-657ecd85e170-1528809265158@3c-app-gmx-bs08> <87efhbdbaz.fsf@Rainer.invalid> <20180613080953.GR7851@calimero.vinschen.de> <trinity-bc977f4a-d31b-4cf6-be60-493433b38724-1528884853707@3c-app-gmx-bs06>
Sven Eden writes:
> True, if /this isn't just a mount point for //this, meaning
> that the "that"s are two different files.
Again, my main objection is that the interpretation of a path should not
change based on the availability or non-availability of any host (or its
name resolution) over the network. That's exactly the kind of thing
that will come back to bite you in the most inconvenient moment.
Regarding the discussion about Linux behaviour, I'd be happy if Linux
had an option to just make any path with two leading slashes throw an
error if that path makes it anywhere a local filesystem gets involved.
That'd be quite helpful in quickly weeding out portability problems like
the one you showed.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple