Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160103112125.ZM12920@torch.brasslantern.com>
Date: Sun, 3 Jan 2016 11:21:25 -0800
In-Reply-To: <20160103190031.24249cf5@ntlworld.com>
Comments: In reply to Peter Stephenson <p.w.stephenson@ntlworld.com>
        "Re: [BUG] functions can't create global readonly variables" (Jan  3,  7:00pm)
References: <56874393.1010001@inlv.org> 
	<160101202710.ZM1896@torch.brasslantern.com> 
	<20160102181814.3ac8d578@ntlworld.com> 
	<160102123639.ZM16270@torch.brasslantern.com> 
	<20160103190031.24249cf5@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: [BUG] functions can't create global readonly variables
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jan 3,  7:00pm, Peter Stephenson wrote:
}
} $ readonly foo=empty
} $ fn() { local foo=bar; echo $foo; }
} $ fn
} bash: local: foo: readonly variable
} empty

I suppose if you consider locality to be a property of the variable,
then making the variable readonly means you can't change that property.

Fortunately readonly in a nested function, where the name is declared
local in the outer function, does work like zsh's "typeset -gr" and
does not force the readonly into truly global scope.