Re: weird problem -- path interpretted/eval'd as numeric expression

[Greg Wooledge]

On Wed, Mar 27, 2013 at 02:37:16PM -0700, Linda Walsh wrote:
> Greg Wooledge wrote:
> >>>       Array variables may not (yet) be exported.
> > Associative arrays can't be exported either.

>       Yeah, but they seem to get propagated anyway, I must save it somewhere 
> like
> I do _FPATH... i.e. each include adds teh included script into the INC array 
> so
> I don't
> try to re-include it.

Well, I'm quite confident that they aren't propagated through the
environment:

imadev:~$ echo $BASH_VERSION
4.2.37(14)-release
imadev:~$ unset foo
imadev:~$ declare -Ax foo=([bar]=baz [quux]=frob)
imadev:~$ declare -p foo
declare -Ax foo='([quux]="frob" [bar]="baz" )'
imadev:~$ bash
imadev:~$ declare -p foo
bash: declare: foo: not found

So, if you're picking up the definition of _FPATH in a child process,
it's coming from something else.  Unless you've got another strange
SuSE patch....