[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: coproc and existing variables
From: |
Chet Ramey |
Subject: |
Re: coproc and existing variables |
Date: |
Tue, 17 May 2016 11:56:08 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0 |
On 5/16/16 4:44 PM, Grisha Levit wrote:
> A couple of minor things after the change (i don’t know if they’re worth
> looking at..)
>
> * If coproc name is a nameref to an unset variable, a nameref/array is
> left over:
What do you think should happen here? Should the coproc code remove the
nameref attribute and use the name supplied to the coproc command as the
name of the array, or should it resolve the nameref and use `x' as the
name of the coproc? I'm interested in opinions here.
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/
- Re: coproc and existing variables, Grisha Levit, 2016/05/16
- Re: coproc and existing variables,
Chet Ramey <=
- Re: coproc and existing variables, Grisha Levit, 2016/05/17
- Re: coproc and existing variables, Chet Ramey, 2016/05/19
- Re: coproc and existing variables, Grisha Levit, 2016/05/23
- Re: coproc and existing variables, Chet Ramey, 2016/05/23
- Re: coproc and existing variables, Grisha Levit, 2016/05/23
- Re: coproc and existing variables, Dan Douglas, 2016/05/24
- Re: coproc and existing variables, Chet Ramey, 2016/05/24