On Sun, Jun 01, 2008 at 01:15:24PM +0000, Clint Adams wrote: > On Sun, Jun 01, 2008 at 12:11:39PM +0100, Stephane Chazelas wrote: > > then, posh has another problem with the other special builtins. > > As far, as I can tell, POSIX doesn't say that special builtin > > names can't be used as functions. > > It says that the command search order is special builtins, then > functions, then regular builtins, then non-built-in commands.
Oh thanks. Sorry, I had missed that. What a strange requirement! Looks like bash and zsh authors found it strange as well as they don't implement it when not called as sh (for zsh, even when called as sh). Another strange requirement that I see no shell implements even posh, is that if a builtin (such as "[" or "echo" or ":") is not found in $PATH, its invocation should fail!?! $ posh -c 'PATH=/; echo "foo"' foo should have given something like: posh: echo: not found instead if I read the standard correctly. [...] > > > It's not a keyword, it's a builtin; what is your basis for the > > > quoting behavior? > > > > keywords are only recognised as keywords when not quoted as the > > quote removal is performed after the recognition of keywords. > > Again, "local" is not a reserved word or keyword. I understood that, I was only answering your question: "what is your basis for the question behavior?". [...] > This particular issue would more productively be discussed in a > bug on the debian-policy package or on the > [EMAIL PROTECTED] mailing list. agreed, that's just me needing my daily ranting ;). Cheers, Stéphane -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
