From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@ifh.de>, Rik Faith <faith@cs.unc.edu>,
zsh-users@math.gatech.edu
Subject: Re: local after setopt allexport?
Date: Thu, 8 Aug 1996 22:44:52 -0700 [thread overview]
Message-ID: <960808224452.ZM21431@candle.brasslantern.com> (raw)
In-Reply-To: Rik Faith <faith@cs.unc.edu> "Re: local after setopt allexport?" (Aug 8, 10:50pm)
On Aug 8, 10:50pm, Rik Faith wrote:
} Subject: Re: local after setopt allexport?
}
} If this is not a compatibility or historical practice issue, I'd like to
} suggest that the commands "local", "typeset", etc. all look like they are
} used to declare the "type" of a variable. As such, it seems that
} "exportable" is a type attribute and that this attribute should be
} associated with a variable for the remainder of its lifetime (or until
} another typeset).
This is in fact what happens when `allexport' is NOT set.
} This could be implemented internally in zsh with a
} tri-state flag: +x for exportable, -x for local, and ?x for "use the
} current state of the allexport option".
It'd have to be +x for local, -x for exported, to be consistent with
existing usage.
I confess to be curious why:
setopt allexport
typeset +x FOO=bar
results in FOO being exported, whereas
setopt allexport
FOO=bar
typeset +x FOO
results in FOO being local. Does ksh really ignore the `+x' in the
first example? (I should get pdksh so I can stop asking this stuff,
but then again, most of the time I don't *want* pdksh.)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
prev parent reply other threads:[~1996-08-09 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-06 19:38 Rik Faith
1996-08-07 7:29 ` Peter Stephenson
1996-08-09 2:50 ` Rik Faith
1996-08-09 5:44 ` Bart Schaefer [this message]
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=960808224452.ZM21431@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=faith@cs.unc.edu \
--cc=pws@ifh.de \
--cc=schaefer@nbn.com \
--cc=zsh-users@math.gatech.edu \
/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).