Re: |& in bash?

[Chet Ramey]

On 1/18/13 4:10 PM, Dan Douglas wrote:

> In scripts it breaks POSIX, conflicts with the coproc operator in kshes, and 
> applies the redirections in an unintuitive order since the same operator 
> redirects stdout first, then applies the stderr redirect after other 
> redirections. It isn't very common to dump multiple streams into one pipe. I 
> suggest avoiding |&.

It doesn't `break' Posix.  Posix doesn't say anything about it, so it's
simply undefined.

It's syntactic sugar.  A parser macro, if you will.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/