I don't even see why we need a magic variable for this. ksh makes you
manually store $! and bash also allows this.
As an alternative, create a special BASH_COPROC_PIDS associative array
to map coproc names to pids. ${foo}_suffix=bar is never as good as an
associative array.
On 5/24/16 1:41 AM, Dan Douglas wrote:
>> You don't precede it with an `exec', so it doesn't affect the current
>> shell. So-called `null' commands with redirections are executed in
>> subshells. This is where you need the `exec'.
>
> I know POSIX allows for a subshell but don't know what the p
On 5/24/16 4:08 AM, Dan Douglas wrote:
> I don't even see why we need a magic variable for this. ksh makes you
> manually store $! and bash also allows this.
OK. I'm not going to go back and remove it.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa,
On Tue, May 24, 2016 at 10:23 AM, Chet Ramey wrote:
> It's not that Posix `allows' a subshell, it requires a subshell
> environment:
Hm sorry I thought it was "may". This is kind of easy to confuse with
all the other unspecified things about side-effects from assignments
affecting subsequent assi
On 5/24/16 12:09 PM, Dan Douglas wrote:
> On Tue, May 24, 2016 at 10:23 AM, Chet Ramey wrote:
>> It's not that Posix `allows' a subshell, it requires a subshell
>> environment:
>
> Hm sorry I thought it was "may". This is kind of easy to confuse with
> all the other unspecified things about side-
Hi, is there a target date for the release of Bash 4.4? Bash seems to
have gone through a lot of changes/bugs lately so it would be nice if
get to test it with my application with its final snapshot before it
gets released so I'm sure it's stable for that major version.
Perhaps mentioning the rel
