Re: [POSIX conformance] "." looks for file in the current directory

[Stephane Chazelas]

On Tue, Jun 10, 2008 at 11:20:54AM +0200, Andreas Schwab wrote:
> Stephane_Chazelas@yahoo.fr writes:
> 
> > SUSv3> Some older implementations searched the current directory
> > SUSv3> for the file, even if the value of PATH disallowed it. This
> > SUSv3> behavior was omitted from this volume of IEEE Std
> > SUSv3> 1003.1-2001 due to concerns about introducing the
> > SUSv3> susceptibility to trojan horses that the user might be
> > SUSv3> trying to avoid by leaving dot out of PATH .
> 
> Ironically, the example just before the rationale depends exactly on
> finding the file in the current directory.
[...]

Indeed, and they forgot to quote variables, and they use "echo"
which they recommand not to use. And at least the HTML version
is missing a line break.

Note that they don't say whether $PATH contains the current
directory, so it's still a valid example. It's just a bit
misleading, they should have used ". ./foobar"

-- 
Stéphane