According to Eric Blake on 8/31/2009 8:08 AM: > Herbert Xu <herbert <at> gondor.apana.org.au> writes: > >>> In other words, if CDPATH is "/", then you should not append any >>> additional <slash> characters, such that you end up checking for the >>> existence of "/foo", not "//foo". >> Fair enough. However, I noticed that they haven't fixed up PATH >> to do the same thing. >> Since we use the same function for PATH and CDPATH, I'm not going >> to make any changes until POSIX becomes consistent in this respect. > Fair enough; I'll keep you posted when the Austin group rules on my report. > http://austingroupbugs.net/view.php?id=139 The Austin Group has now made their ruling; there is a 30 day clock before the interpretation becomes official, but consensus will probably be granted to the proposed wording: > Interpretation response > ------------------------ > The standard states the requirements for PATH > and conforming implementations must conform to this. However, concerns > have been raised about this which are being referred to the sponsor." > > Rationale: > ------------- > This is for consistency with the previous change to CDPATH made in interpretation 1003.1-2001 #199 > https://www.opengroup.org/austin/interps/uploads/40/15188/AI-199.txt [^] > > > Notes to the Editor (not part of this interpretation): > ------------------------------------------------------- > At line 5674, replace the sentence: > > When a nonzero-length prefix is applied to this filename, a <slash> shall be inserted between the prefix and the filename. > > with: > > When a nonzero-length prefix is applied to this filename, a <slash> shall be inserted between the prefix and the filename if the prefix did not end in <slash>. -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -- To unsubscribe from this list: send the line "unsubscribe dash" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html