From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [BUG] Can't mark unset variables as read-only
Date: Wed, 29 Apr 2015 06:55:56 -0700 [thread overview]
Message-ID: <150429065556.ZM31553@torch.brasslantern.com> (raw)
In-Reply-To: <20150429113602.374240c7@pwslap01u.europe.root.pri>
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?)
defeats the whole purpose of an unset readonly?
Actually it probably undermines readonly for variables that are set, too,
so I probably shouldn't worry about it because it isn't changing.
next prev parent reply other threads:[~2015-04-29 13:56 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 [this message]
2015-04-29 14:41 ` Peter Stephenson
2015-04-29 15:33 ` Chet Ramey
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=150429065556.ZM31553@torch.brasslantern.com \
--to=schaefer@brasslantern.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).