[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 09:57:06 -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 1:15 AM, Great Big Dot wrote:
> Bash Version: 4.4
> Patch Level: 23
> Release Status: release
>
> Description:
> The builtin array variable FUNCNAME (which provides a way to trace the
> stack of functions called so far) appears to be unset according to certain
> bash expansions, even when it isn't. If the following code is saved to a
> file and executed (this doesn't work at the command line), the problems
> begin to appear:
>
> printf -- '%q\n' "${FUNCNAME}"
> printf -- '%q\n' "${FUNCNAME[0]}"
> printf -- '%q\n' "${FUNCNAME[*]}"
Thanks for the report. It should expand to the empty string in all these
cases.
--
``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/