From: Chet Ramey <chet.ramey@case.edu>
To: Peter Stephenson <p.stephenson@samsung.com>, zsh-workers@zsh.org
Cc: chet.ramey@case.edu
Subject: Re: [BUG] Can't mark unset variables as read-only
Date: Wed, 29 Apr 2015 11:33:10 -0400 [thread overview]
Message-ID: <5540F9B6.5020805@case.edu> (raw)
In-Reply-To: <20150429154136.152b7b05@pwslap01u.europe.root.pri>
On 4/29/15 10:41 AM, Peter Stephenson wrote:
> On Wed, 29 Apr 2015 06:55:56 -0700
> Bart Schaefer <schaefer@brasslantern.com> wrote:
>
>> On Apr 29, 11:36am, Peter Stephenson wrote:
>> }
>> } +Note that in zsh (unlike other shells) it is still possible
>> } +to create a local variable of the same name as this is considered a
>> } +different variable (though this variable, too, can be marked readonly).
>>
>> Hrm, I wonder if that, combined with "typeset" automatically creating
>> locals when called in a function context (also a POSIX incompatibility?)
It's not a Posix incompatibility; Posix does not specify typeset or local
variables at all. The Posix-conformant ways of declaring variables in a
function result in global variables, as Posix specifies.
>> defeats the whole purpose of an unset readonly?
The question is whether or not you can use local variables to `shadow'
readonly variables in a previous scope. Bash doesn't allow you to do
that. Given this script:
readonly foo=immutable
func()
{
local foo=bar
echo inside: $foo
}
func
echo outside: $foo
Bash gives the following output:
./x26: line 5: local: foo: readonly variable
inside: immutable
outside: immutable
If the purpose of readonly is to make a particular name/value pair
immutable, I think that allowing a local variable to shadow it,
especially if you're going to export that local variable, is a bad thing.
>
> I don't think so... bash makes these local, too:
>
> $ foo=bar
> $ fn() { typeset foo=something_else; echo $foo; }
> $ fn
> something_else
> $ echo $foo
> bar
>
> So "foo" in fn is logically something entirely different and I don't
> think there's any requirement for it to be treated as readonly;
There's no requirement, since there are no standards for local variables
or variable scoping. Bash does what I think is right.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
next prev parent reply other threads:[~2015-04-29 15:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 6:35 Martijn Dekker
2015-04-29 10:36 ` Peter Stephenson
2015-04-29 10:57 ` Mikael Magnusson
2015-04-29 11:01 ` Mikael Magnusson
2015-04-30 0:08 ` PATCH: Don't define internal params directly in hook function scope Mikael Magnusson
2015-04-30 4:01 ` Bart Schaefer
2015-04-30 8:44 ` Peter Stephenson
2015-04-30 11:18 ` Peter Stephenson
2015-04-29 11:09 ` Local readonly specials (was: Can't mark unset variables as read-only) Peter Stephenson
2015-04-29 13:46 ` [BUG] Can't mark unset variables as read-only Martijn Dekker
2015-04-29 13:55 ` Bart Schaefer
2015-04-29 14:41 ` Peter Stephenson
2015-04-29 15:33 ` Chet Ramey [this message]
2015-04-29 19:09 ` Stephane Chazelas
2015-04-29 23:22 ` Chet Ramey
2015-04-30 3:57 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2015-04-29 5:48 Martijn Dekker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5540F9B6.5020805@case.edu \
--to=chet.ramey@case.edu \
--cc=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).