Eric Blake wrote:
> On 07/25/2011 03:45 PM, Linda Walsh wrote:
>> I mistyped that but it brings me to an interesting
>> conundrum:
>>
>> GLOBAL="hi there"
>> {foo=GLOBAL echo ${!foo}; }
>
> This says:
>
> evaluate ${!foo}, and pass that expansion to 'echo', with foo=GLOBAL in
> the environment of echo. You are invoking behavior that POSIX leaves
> undefined...
>
>> Weird...
>
> Not if you think about it properly.
---
Didn't think it was a bug. just 'odd', and that's because
it falls into a POSIX undefined case, that could really
go 'either way'...as you seemed to state.
I didn't know why it behaved differently, but as you informed me
the difference is 'one's well-defined, and the other is not, I can
see why there 'could' be a difference... ;-)
(which of course could change tomorrow, I suppose..)
