[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: namref dicussion continued: [PATCH] export -r reference
From: |
Dan Douglas |
Subject: |
Re: namref dicussion continued: [PATCH] export -r reference |
Date: |
Mon, 9 May 2016 00:57:43 -0500 |
On Sun, May 8, 2016 at 6:03 PM, Chet Ramey <chet.ramey@case.edu> wrote:
> On 5/5/16 6:02 PM, Dan Douglas wrote:
>> On Thu, May 5, 2016 at 2:46 AM, Piotr Grzybowski <narsil.pl@gmail.com> wrote:
>>> ok, so Dan wants this patch.
>>
>> Yes I think your bash patch is probably an improvement at least in
>> this particular case.
>>
>>> Maybe you can comment on wether the patches are valid.
>>
>> The posix export and readonly don't produce locally scoped variables
>> at all, so it's expected that e.g. `typeset -x` and `export` will
>> differ.
>
> This is a different topic entirely, since neither of the examples
> we're considering take place within a function. Scoping isn't an
> issue.
Sure I agree that scope isn't the issue. That's was the main point of
my message. I was trying to explain is that ksh does allow -x in
combination with pre-existing references in some contexts, but the
only way to demonstrate that is by calling a function.
Re: namref dicussion continued: [PATCH] export -r reference, Chet Ramey, 2016/05/08