From: Martijn Dekker <martijn@inlv.org>
To: zsh-workers@zsh.org
Subject: Re: [BUG] Can't mark unset variables as read-only
Date: Wed, 29 Apr 2015 15:46:00 +0200 [thread overview]
Message-ID: <5540E098.5070509@inlv.org> (raw)
In-Reply-To: <20150429113602.374240c7@pwslap01u.europe.root.pri>
Peter Stephenson schreef op 29-04-15 om 12:36:
> As you can imagine,
> something like this that completely breaks the normal programming model
> of variables (a variable can't have state if it's unset because it
> doesn't exist) is a nightmare to implement;
FWIW, I imagine a simpler way might be, rather than implementing
read-only as an attribute of variables themselves, to keep a separate
table of variable names marked as read-only which is checked against
upon variable assignment.
I know absolutely nothing about the zsh codebase, so feel free to laugh
at my suggestion. My interest is in getting the most out of
cross-platform shell programming, and I'm really only here to report a bug.
Many thanks for the patch. I'll apply it, test it, and report back.
(Also, my apologies for the initial duplicate. I thought it hadn't gone
through the first time.)
- Martijn
next prev parent reply other threads:[~2015-04-29 13:46 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 ` Martijn Dekker [this message]
2015-04-29 13:55 ` [BUG] Can't mark unset variables as read-only Bart Schaefer
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=5540E098.5070509@inlv.org \
--to=martijn@inlv.org \
--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).