Hi Paul, Thanks for the answers!
Le 25 mai 2012 à 23:32, Paul Eggert a écrit : > On 05/25/2012 01:45 AM, Akim Demaille wrote: > >> OK, thanks! Actually I see also that you made efforts >> to leave a single slash, even if DIR ended with many. >> Is this aesthetics, or is there some semantical difference >> that might result? > > I expect it was for the hosts where "//x" is different > from "/x". That is, normally any nonempty sequence of > slashes is equivalent to one slash, but there's an exception > for file names that start with exactly two slashes. POSIX > allows this exception -- it was originally for the Apollo > Domain, if memory serves, and I think Cygwin still uses it. Should I submit a patch to gnulib to implement this in concatenated_filename? I expect the answer is yet, for Cygwin, not for Apollo :) >> Do you recommend turning -DGNULIB_POSIXCHECK on and >> blindly obey to it to get a warning-free compilation? > > I'd say "no", given the examples you've mentioned so far, since > they've all been incorrect changes introduced to avoid the warnings. > If memory serves, the GNULIB_POSIXCHECK stuff is for portability to > Microsoft operating systems other than Cygwin, which are low priority > for the GNU project. Your limited time is probably better spent > elsewhere. Thanks, this is helpful! I'll adjust README-hacking accordingly.
