[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: |& in bash?

From: Chet Ramey
Subject: Re: |& in bash?
Date: Sat, 19 Jan 2013 14:47:38 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0

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.

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]