Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160101202710.ZM1896@torch.brasslantern.com>
Date: Fri, 1 Jan 2016 20:27:10 -0800
In-Reply-To: <56874393.1010001@inlv.org>
Comments: In reply to Martijn Dekker <martijn@inlv.org>
        "[BUG] functions can't create global readonly variables" (Jan  2,  4:27am)
References: <56874393.1010001@inlv.org>
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 2,  4:27am, Martijn Dekker wrote:
}
} It is apparently impossible to create global readonly variables from
} within a function.

    typeset -gr var=value
or
    readonly -g var=value

} I don't know if this is intended behaviour for native zsh mode; the
} 'zshbuiltins' man page does not mention anything about this.

Of course it does:

    readonly
	 Same as typeset -r.

    typeset ...
	 Set or display attributes and values for shell parameters.

	 A parameter is created for each NAME that does not already refer
	 to one.  When inside a function, a new parameter is created for
	 every NAME (even those that already exist), and is unset again
	 when the function completes.

} But it is certainly a bug for POSIX/'emulate sh' mode.

I think it's undefined behavior for POSIX/'emulate sh'.  Certainly bash
agrees with us:

$ foo() { typeset -r bar; typeset -p bar; }
$ foo
declare -r bar
$ typeset -p bar
bash: typeset: bar: not found