I think I'm more with Simon on this issue.
Shouldn't the unix impl of the symlink resolving care about .. standing
for the parent dir, instead of making users of the nsIFile stuff special
case the mac each time.
It's a bad thing that file paths aren't xp, but make it so. I'd say, if
you need the logic of '..' for symlink resolving, put the logic into
symlink resolving, and have the implementation of Append be really xp.
Of course, creating a dir or a file '..' on unix (and win?) doesn't
work.
I wonder if nsIFile could somehow expose that a particular path is not
portable. As most people wouldn't know what you can really do.
I for one would have bet that you could create filenames with '/' just
by escaping, and it doesn't work. Screw me.
Axel
