[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The builtin array variable 'FUNCNAME' is considered unset by many ex

From: Chet Ramey
Subject: Re: The builtin array variable 'FUNCNAME' is considered unset by many expansions, even when set.
Date: Thu, 8 Nov 2018 10:38:01 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.3.0

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    address@hidden    http://tiswww.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]