From: Chet Ramey <chet.ramey@case.edu>
To: Stephane Chazelas <stephane.chazelas@gmail.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 19:22:18 -0400 [thread overview]
Message-ID: <554167AA.1000209@case.edu> (raw)
In-Reply-To: <20150429190909.GB5530@chaz.gmail.com>
On 4/29/15 3:09 PM, Stephane Chazelas wrote:
> 2015-04-29 11:33:10 -0400, Chet Ramey:
> [...]
>> 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 agree.
OK, we can disagree.
--
``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 23:22 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
2015-04-29 19:09 ` Stephane Chazelas
2015-04-29 23:22 ` Chet Ramey [this message]
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=554167AA.1000209@case.edu \
--to=chet.ramey@case.edu \
--cc=stephane.chazelas@gmail.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).