From: Nicolas C. <war...@fr...> - 2003-11-15 01:08:21
|
> > > Note : this does not actually do any system checking ( the path may not > > > exists or contains invalid characters ). Only special paths . .. and / ( and > > > windows drive letters ) are recognized as special. > > > > No characters are special in unix paths beside '/'. Special paths are > > only "." and ".." (and maybe "/"). Of course this also depends on > > filesystem, but most native FSes allow anything. > > It's not clear that you can do this independently of the OS interface. > For example, to handle a/b/../c correctly, you need to check whether > "b" is a symbolic link and interpret it accordingly. It's true. But when you're doing a/b/../c , do you actually really now what you're doing ? :) Theses kind of things should be marked as "features", not "bug". Nicolas Cannasse |