Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14777

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

Show all headers | View raw

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/

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 09:57 -0500

csiph-web