Re: Understanding internal variable scope

[Chet Ramey]

On 5/28/22 10:36 AM, Robert E. Griffith wrote:

> 1) I find that when my loadable builtin is called from a bash function,
> sometimes the following code works to create a local variable in the
> calling function and sometimes it does not. If I do "local myVariableName"
> before calling the builtin, it always receives hte value.
> 
>    bind_variable_value(make_local_variable("myVariableName",0),
> "SomeValue..., 0)

There would have to be a more reproducible example to say why.

> 2) There seems to be a difference between sourcing a script at global scope
> as opposed to sourcing it from inside a bash function but I cant quite pin
> it down. Sometimes variables declared in the global scope "declare <myvar>"
> of a sourced script do not exist after sourcing the script but functions
> from the script always do.

Variables declared using `declare' when bash is executing inside a
function, whether it's from a sourced script or not, should always be
local, with the usual scoping and `shadowing' rules. There are no such
things as local functions.

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