From: Rich Salz <rsalz@bbn.com>
To: malte@techfak.uni-bielefeld.de, rc@archone.tamu.edu
Subject: Re: export of variables and functions
Date: Fri, 27 Sep 1991 08:29:11 -0500 [thread overview]
Message-ID: <9109271329.AA22899@litchi.bbn.com> (raw)
Byron and I have exchanged messages about this. He rightly says that
the default must be to export something, rather than not export it
otherwise old scripts will break.
My idea of unexporting is to have a variable that names the variables to
not be exported. This seems better then having two new commands, export
and unexport, and makes the "is this variable exported?" test very easy to
write.
fn local { unexported=( $unexported $* ) }
/r$
next reply other threads:[~1991-09-27 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-09-27 13:29 Rich Salz [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-09-27 14:24 Donn Cave
1991-09-27 10:02 malte
1991-09-27 16:04 ` Chris Siebenmann
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=9109271329.AA22899@litchi.bbn.com \
--to=rsalz@bbn.com \
--cc=malte@techfak.uni-bielefeld.de \
--cc=rc@archone.tamu.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.
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).