Duncan Murdoch <[EMAIL PROTECTED]> writes: > Gabor Grothendieck pointed out a bug to me in list.files(..., > full.name=TRUE), that essentially comes down to the fact that in > Windows it's not always valid to add a path separator (slash or > backslash) between a path specifier and a filename. For example, > > c:foo > > is different from > > c:\foo > > and there are other examples. > > I'm going to fix this, but I'm wondering whether the fix is needed > just for Windows, or for Unix too. Specifically: > > In Unix-like systems, is it *always* safe to add a slash between a > pathname and a filename? > > The only examples I can think of that might go wrong are things like > > //foo > > /tmp//foo > > Are these the same as > > /foo > > and > > /tmp/foo? Are there any examples where an extra slash causes trouble?
Also, and of course, if the first part is empty, foo and /foo are very different. There could be a problem with leading //, or is that Windows only? -- O__ ---- Peter Dalgaard Blegdamsvej 3 c/ /'_ --- Dept. of Biostatistics 2200 Cph. N (*) \(*) -- University of Copenhagen Denmark Ph: (+45) 35327918 ~~~~~~~~~~ - ([EMAIL PROTECTED]) FAX: (+45) 35327907 ______________________________________________ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
