This is a discussion on Re: make: evaluation of symbolic link with ../ fails - FreeBSD ; On Tue, 06 Nov 2007 17:20:14 +0100 "Julian H. Stacey" wrote: > It seems to me that all except csh (including bourne shell !) are > broken !! Amazing ! None of them cope properly actually following > symbolic links, ...
On Tue, 06 Nov 2007 17:20:14 +0100 "Julian H. Stacey"
> It seems to me that all except csh (including bourne shell !) are
> broken !! Amazing ! None of them cope properly actually following
> symbolic links, they all make false premise the /some_path/.. ==
> /some_path !
That's not a bug, that's a feature. When symlinks were introduced in
4.1c (or thereabouts), people were often surprised to do:
$ cd /some_path/child
$ cd ..
and not wind up in /some_path, or having the ever popular sh loop:
$ for dir in
$ cd $dir
$ cd ..
start working on something totally unrelated to the current directory
halfway through the loop. So sh (and etc.) added a feature so that
those things worked the way users expected them to.
Basically, the shells don't make a false premise that /some_path/.. ==
/some_path, they make the premise appear to be true as a feature.
Independent Network/Unix/Perforce consultant, email for more information.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "email@example.com"