Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Chet Ramey <chet.ramey@case.edu>
Newsgroups: gnu.bash.bug
Subject: Re: test -v for array does not work as documented
Date: Sun, 23 Feb 2020 13:05:57 -0500
Organization: ITS, Case Western Reserve University
Lines: 35
Approved: bug-bash@gnu.org
Message-ID: <mailman.1453.1582480579.2412.bug-bash@gnu.org>
References: <mailman.4206.1582208094.2410.bug-bash@gnu.org> <w6gh7zlz4de.fsf@kph.uni-mainz.de> <a07dd152-b50a-a77b-13c1-fc559b053fdd@case.edu> <25b3fccb-151b-0712-76f1-5b19ffcce1d9@passchier.net> <9a084bb5-2362-b140-f3e8-9e18a0f1cac6@case.edu> <b7c08d7f-c41d-e4e4-c64f-df805518d753@passchier.net> <c4ab5d47-79b8-14b7-df3b-81acf425fa19@case.edu>
Reply-To: chet.ramey@case.edu
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: chet.ramey@case.edu
To: pepa65 <solusos@passchier.net>, bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Autocrypt: addr=chet.ramey@case.edu; prefer-encrypt=mutual; keydata= mQGiBEEOsGwRBACFa0A1oa71HSZLWxAx0svXzhOZNQZOzqHmSuGOG92jIpQpr8DpvgRh40Yp AwdcXb8QG1J5yGAKeevNE1zCFaA725vGSdHUyypHouV0xoWwukYO6qlyyX+2BZU+okBUqoWQ koWxiYaCSfzB2Ln7pmdys1fJhcgBKf3VjWCjd2XJTwCgoFJOwyBFJdugjfwjSoRSwDOIMf0D /iQKqlWhIO1LGpMrGX0il0/x4zj0NAcSwAk7LaPZbN4UPjn5pqGEHBlf1+xDDQCkAoZ/VqES GZragl4VqJfxBr29Ag0UDvNbUbXoxQsARdero1M8GiAIRc50hj7HXFoERwenbNDJL86GPLAQ OTGOCa4W2o29nFfFjQrsrrYHzVtyA/9oyKvTeEMJ7NA3VJdWcmn7gOu0FxEmSNhSoV1T4vP2 1Wf7f5niCCRKQLNyUy0wEApQi4tSysdz+AbgAc0b/bHYVzIf2uO2lIEZQNNt+3g2bmXgloWm W5fsm/di50Gm1l1Na63d3RZ00SeFQos6WEwLUHEB0yp6KXluXLLIZitEJLQwQ2hldCBSYW1l eSAoQ2FzZSBzdGFuZGFyZCkgPGNoZXQucmFtZXlAY2FzZS5lZHU+iF8EExECAB8FAkPi19EC GwMHCwkIBwMCAQMVAgMDFgIBAh4BAheAAAoJELtYafBk6nSrelkAn31Gsuib7GcCZHbv5L5t VKYR9LklAJ4hzUHKA49Z0QXR+qCb80osIcmPSbkBDQRBDrBvEAQAkK6TAOKBEM+EC4j6V/7o /riVZqcgU5cid2qG9TXdwNtD9a3kvA/ObZBO93sX59wc6Bnwo4VJxsOmMlpGrAjJsxNwg3QH akEtf8LXRbVpj5xStdmBdQZUhIQyalo/2/TZq5OijtddUQcL5cs70hTv/FpT3wUvr2Xr8rjF 41IFEz8AAwcD/A0CZEGlzIrT5WCBnl6xBog/8vKiUCbarByat3d1mL6DbizvKNXQRTC9E/vE dENAWCQCjr75Bu55xT8n3SXGtWdDC5xmZ/P3OBYORP8yl8H8I1FIosWOFirbIeYdZPq8SPD1 HL+EXo9zSiHVrrZRJ19ooCKKbSdXHFCY+aJG+0KZiEkEGBECAAkFAkEOsG8CGwwACgkQu1hp 8GTqdKvjcACfZlkVCDwaz/NTO9cy3t69oWpVPNwAnRwe0qk/WL/gfhH346xh5B3HFbFN
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
In-Reply-To: <b7c08d7f-c41d-e4e4-c64f-df805518d753@passchier.net>
Content-Language: en-US
Precedence: list
Xref: csiph.com gnu.bash.bug:15953

On 2/23/20 11:36 AM, pepa65 wrote:
> On 23/02/2020 23.27, Chet Ramey wrote:
>> On 2/21/20 3:31 AM, pepa65 wrote:
>>> By the way, it seems that `local -p var` doesn't work like 'declare -p
>>> var` even though `help local` suggests it should.
>>
>> How so? Do you mean that declare -p var in a function will show different
>> variables?
> 
> See this output:
> 
> localvsdeclare(){
>   local var
>   var=42
>   unset var
>   echo -n '"declare -p var":'
>   declare -p var
>   echo -n '"local -p var":'
>   local -p var
> }
> 
> localvsdeclare
> "declare -p var": declare -- var
> "local -p var":

Yes, it's always been this way. This behavior dates to March, 1995,
literally to the time I added `-p'. The reason for not making `local -p'
work the same has been lost to time, so let's try making it the same
and see what happens.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/