Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14780 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-11-08 10:38 -0500 |
| Last post | 2018-11-08 10:38 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-11-08 10:38 -0500 |
| Subject | Re: The builtin array variable 'FUNCNAME' is considered unset by many expansions, even when set. |
| Message-ID | <mailman.3658.1541691497.1284.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web