Re: The builtin array variable 'FUNCNAME' is considered unset by many expansions, even when set.

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: The builtin array variable 'FUNCNAME' is considered unset by many expansions, even when set.
Date	2018-11-08 10:38 -0500
Message-ID	<mailman.3658.1541691497.1284.bug-bash@gnu.org> (permalink)
References	<CAN6vQO8zM7DwE2ftcy2vRTKQxPAKrf9LaQ3EPfaNRGpVjdg+zg@mail.gmail.com> <6f4639e1-b55c-1d48-94b6-b6d425401ace@case.edu> <CAN6vQO-s+Net_etHgm3n80zrU4VbrXjArW+ved_mzgbKbCy4-g@mail.gmail.com>

Show all headers | View raw

On 11/8/18 10:28 AM, Great Big Dot wrote:
>> It should expand to the empty string in all these cases.
> 
> Oh yeah, right, because a function isn't even running. Duh. All my comments
> about expected behavior should be inverted, then, I guess. Out of
> curiosity, do you have any idea what's causing bash to *sometimes*
> correctly conclude that FUNCNAME[0] is empty and other times that
> FUNCNAME[*] is empty, under seemingly arbitrary circumstances? I can't
> figure out what could be causing that.

Yes. The internal function that returns an array value isn't honoring the
`not visible' setting. That's where the change needs to be.

-- 
``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/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: The builtin array variable 'FUNCNAME' is considered unset by many expansions, even when set. Chet Ramey <chet.ramey@case.edu> - 2018-11-08 10:38 -0500

csiph-web