[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: param expansion with single-character special vars in the environmen
|
From: |
Chet Ramey |
|
Subject: |
Re: param expansion with single-character special vars in the environment |
|
Date: |
Tue, 3 May 2016 13:54:34 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0 |
On 4/28/16 5:20 PM, Grisha Levit wrote:
>
> On Thu, Apr 28, 2016 at 3:14 PM, Piotr Grzybowski <narsil.pl@gmail.com
> <mailto:narsil.pl@gmail.com>> wrote:
>
> b. we can forbid
> # declare -n T
> when T is a readonly variable
>
>
> This is the one that makes the most sense to me. It shouldn't however be
> forbidden to do `declare -nr RO=foo' if RO is not already a readonly variable.
Interesting that ksh93 throws a usage error when presented with that (using
typeset, of course).
--
``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: param expansion with single-character special vars in the environment, Chet Ramey, 2016/05/02
Re: param expansion with single-character special vars in the environment, Chet Ramey, 2016/05/02
Re: param expansion with single-character special vars in the environment,
Chet Ramey <=
Re: param expansion with single-character special vars in the environment, Chet Ramey, 2016/05/06