Date: Sat, 16 Jun 2001 01:24:19 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: Bruce Evans <bde@zeta.org.au>, freebsd-current@FreeBSD.ORG Subject: Re: tcsh.cat Message-ID: <20010616012418.A21715@nagual.pp.ru> In-Reply-To: <200106151953.PAA25655@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Fri, Jun 15, 2001 at 03:53:10PM -0400 References: <200106151308.OAA07742@rhymer.cogsci.ed.ac.uk> <Pine.BSF.4.21.0106152325320.84795-100000@besplex.bde.org> <200106151953.PAA25655@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 15, 2001 at 15:53:10 -0400, Garrett Wollman wrote: > <<On Fri, 15 Jun 2001 23:33:07 +1000 (EST), Bruce Evans <bde@zeta.org.au> said: > > > Here's an example of a complication: what is the semantics of /tmp/foo/bar > > where foo is a symlink to ""? I think the pathname resolves to > > /tmp//bar and then to /tmp/bar, but this is surprising since foo doesn't > > point anywhere. > > But this is at least consistent with the historic (pre-POSIX) behavior > where the filename "" is equivalent to ".". POSIX explicitly disallow "" filenames everywhere. I think it should be so for symlinks too. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010616012418.A21715>