While debugging a related bug - 3185609 - I discovered the following issue.
Windows treats path components containing only "." differently from Tcl. If a path component contains more than 2 dots, Windows treats this the same as a single "." so c:/foo/bar/... (three dots in last component), is the same as c:/foo/bar/.
Tcl, on the other hand, treats the path as a valid path with the tail being "...". This is what gets cached as the "normalized path" in various fields in the FSPathObj.
Not sure what the external ramifications are (for example, code that compares paths after normalization would not result the same result as Windows) and it's a corner case anyways (Only happened to type in ... instead of .. by mistake) but just recording this inconsistency in case there might be bigger ramifications (security?) that I haven't thought of.
|