BASH and Posix Redirection.

[chris . bitmead]

>It depends on your definition of `correctness'.  Bash does what POSIX
>specifies.

Well Posix specifies that  ./{foo,bar,baz} is not expanded, but bash does it
because it is nice
and it doesn't hurt anybody. And bash supports other things that support bourne
compatibility
even though Posix doesn't cover it.

It's nice to be able to list the pipline in logical order...
<input prog1 | prog2 | prog3 >output
Very logical, having input first, output last.

Pretty wierd that if one of the intervening commands is deemed a "compound"
command,
it should be rejected.

Why must bash be a slave to POSIX when posix is dumb, and having the extension
hurts nobody?

(BTW, like most people I'm not going to be patching every copy of bash I have to
use on every machine I use so I can make it work).

Do we acknowledge that the CDPATH thing is a bug?