> > Further, if your process is treating '..' as a subdirectory, you're doing it wrong. > That's the point they make. And in Unix, it's really easy to do it th

> > Further, if your process is treating '..' as a subdirectory, you're doing it wrong. > That's the point they make. And in Unix, it's really easy to do it the "wrong" way (like, "type 3 characters" easy), so lots of people do. The OP is writing about iterating subdirectories and accidentally treating ".." as such, if you use certain low level functions - which is kind of bad practice in most cases anyway. > That's the point they make. And in Unix, it's really easy to do it the "wrong" way (like, "type 3 characters" easy), so lots of people do. Yeah, pointing to a wrong directory can lead to unexpected results. On the other hand, if this becomes a security issue, then maybe the process should have properly restricted rights as pointed out elsewhere already. Talking about "..", one could BTW extend the discussion to mixing Filename characters with path separator characters in the same string. ;)